-
Notifications
You must be signed in to change notification settings - Fork 148
fix: revert webmodeler externaldb change #4071
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
Conversation
| .Values.webModeler.restapi.externalDatabase.host | ||
| (toString (.Values.webModeler.restapi.externalDatabase.port)) | ||
| (.Values.webModeler.restapi.externalDatabase.database) | ||
| -}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like we're dropping support for externalDatabase.host, externalDatabase.port, and so on.
We normally do not just drop support for options like this. we typically talk with product management about a timeframe schedule notifying users of the setting to be removed, and a schedule for removal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot it was added to 8.7, too. I think it's simpler to just remove the deprecation notice for now and make no functional changes
jessesimpson36
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs to be a conversation with product-management.
This reverts commit 3857e26.
…munda/camunda-platform-helm into 4046-webmodeler-db-url-revert
Which problem does the PR fix?
Closes: #4046
What's in this PR?
Revert prior webmodeler DB change, favoring JDBC URL only configuration
Checklist
Please make sure to follow our Contributing Guide.
Before opening the PR:
make go.update-golden-only.After opening the PR: