-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Is the quarkus openapi generator extension used for escalation ? #29
Comments
@cmoulliard The openAPI-related code is generated by the Maven build, so please run |
That move is not required, according to the SonataFlow specs and to all of our tests until today.
Let me add some env as well:
|
That works :-). The issue was perhaps related to tree of folders under target not refreshed by IntelliJ
|
So the answer to my question is: The quarkus openapi generator is executed by "kogito-quarkus-serverless-workflow" and the following properties defined part of the application.properties file are not used for that purpose
So I suspect that the property
will call the Kube API (using java generated classes) to request to the cluster to create a namespace - correct ? Question: Will this property |
I think that all the OpenAPI clients are using these bearer tokens the same way, no matter the server is Kube or any other service. securitySchemes:
BearerToken:
type: http
scheme: bearer
description: Bearer Token authentication Adding @ricardozanini who can help in finding the right person to reply any further doubts |
@cmoulliard @dmartinol your assumptions are correct. The I'd recommend reading https://docs.quarkiverse.io/quarkus-openapi-generator/dev/client.html. If there's anything I can help or dubious in the docs, let me know so we can fix it. |
Do you created the |
@cmoulliard IIRC @rgolangh created it initially, I think by reducing some published specs to reduce the size of the ConfigMap. Once he returns from the business trip I'm sure he can help |
@cmoulliard speaking about the general use case, users will have to make the files available in that path and then configure the |
@cmoulliard you can also look at this option to share the same API specs and reuse it in multiple workflows: Using URI alias |
Question
Is the quarkus openapi generator extension used by escalation example to generate the OpenAPI YAML file of kube ?
I'm confused as the properties file includes the following property
quarkus.openapi-generator.kube_yaml.auth.BearerToken.bearer-token=${OCP_API_SERVER_TOKEN}
- see:https://github.com/parodos-dev/serverless-workflow-examples/blob/main/escalation/src/main/resources/application.properties
BUT I don't see anything generated under
src/main/openapi
Can you explain what you did to generate the YAML file of kube and if you generated also some java client classes ?
The text was updated successfully, but these errors were encountered: