This repository has been archived by the owner on Oct 20, 2022. It is now read-only.
[DRAFT] add ability to override default authorizers.xml template #170
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.
What's in this PR?
This is an attempt at adding support for overriding the default authorizer configuration. I've put this in [DRAFT] status until the approach is given a 👍 , @erdrix .
Adds
ReadOnlyConfig.AuthorizerConfig
with two properties:ReplaceTemplateConfigMap
ReplaceTemplateSecretConfig
These are ConfigMap or Secret refs to override the default
authorizers.xml
template. The docs clarify this, but the order of precedence follows similar conventions for other configurations:Secret > ConfigMap > default
The purpose of this PR is to configure a custom authorizer, userGroupProvider, and accessPolicyProvider.
Why?
It's not possible to configure an authorizer other than
managed-authorizer
oruserGroupProvider
/accessPolicyProvider
other than the file-based ones.Checklist
To Do