-
Story
-
Resolution: Unresolved
-
Major
-
1.35.0
-
None
Description
Currently, when invoking OpenAPI REST services from SonataFlow, users must configure static options in their Quarkus applications, such as:
quarkus.rest-client.openapi_yaml.url=http://server1 quarkus.openapi-generator.openapi_yaml.auth.basic.username=alice quarkus.openapi-generator.openapi_yaml.auth.basic.password=${SECRET}
This static configuration approach limits flexibility, making it challenging for workflow developers to dynamically set these parameters within the workflow definition using tools like jq or data manipulation contexts.
Objective:
Enhance SonataFlow to allow dynamic specification of OpenAPI service URLs and security credentials directly within the workflow definitions, enabling greater flexibility and adaptability in various deployment scenarios.
Acceptance Criteria
- [ ] Implement functionality to dynamically set OpenAPI service URLs within workflow definitions.
- [ ] Enable dynamic configuration of security credentials (e.g., basic auth username and password) within workflow definitions.
- [ ] Ensure compatibility with existing Quarkus configurations.
- [ ] Update documentation to guide users on utilizing dynamic configurations in workflow definitions.
- [ ] Provide test coverage for dynamic URL and security configuration features.
- is depended on by
-
FLPATH-2305 [RO] - Workflow execution fails with 404 - openshift-deployments-openapi_patchAppsV1NamespacedDeployment
-
- Closed
-
- links to