Identity for cluster clients in 8.7 Clusters #4803
Draft
+4
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related to: https://github.com/camunda/product-hub/issues/2222
The way Custer API clients are manages will change with the 8.7 Identity Integration.
In Console Clients can still be created, but all scopes (except for the
Secrets
Scope) will be managed in the Cluster Identity Deployment.Afaik, currently the Identity Documentation does not exist. But the Console API client documentation should refer to the Identity Documentation. (Link in this change is a placeholder)
When should this change go live?
hold
label or convert to draft PR)PR Checklist