Skip to content
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

Environment based dynamic URL for the RestConnector #2419

Open
siteshkumarpati opened this issue May 2, 2024 · 1 comment
Open

Environment based dynamic URL for the RestConnector #2419

siteshkumarpati opened this issue May 2, 2024 · 1 comment
Labels
kind:enhancement New feature or request

Comments

@siteshkumarpati
Copy link

siteshkumarpati commented May 2, 2024

Is your feature request related to a problem? Please describe.

In Camunda-7, we had provisions where we can call the Java code to set the dynamic URLs, headers for the HTTP connector from the same task using expression. But as of now in Camunda-8, process can only read URL values from process variables, so we need to get the URLs, headers before calling the REST connector.

Describe the solution you'd like

I am able to use process variable for the URL in RestConnector (Camunda 8 RestConnector).
My requirement is to decide the environment(QA,DEV,PROD) specific URL for the RestConnector at runtime. Is it possible to populate the URL for the RestConnector by calling java code? (This java code will help in deciding RestConnector URL by using Spring Profiles )

Describe alternatives you've considered

NA

Additional context

NA

@siteshkumarpati siteshkumarpati added the kind:enhancement New feature or request label May 2, 2024
@sbuettner
Copy link
Contributor

Hi @siteshkumarpati and thanks for your request.

Did you try to make use of https://docs.camunda.io/docs/components/connectors/use-connectors/#using-secrets for the url you want to call?

Are you running on SaaS or are you using a self-managed instance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants