[Authz] Enabled no_deprecated_authz_config for migration only #196852
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elena-shostak
added
the
Team:Security
|
Pinging @elastic/kibana-security (Team:Security) |
elena-shostak
added
Feature:Security/Authorization
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
|
Ikuni17
approved these changes
Oct 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
To ensure that
no_deprecated_authz_configrule is only applied during an intentional migration, added check for env vars presence.If neither
MIGRATE_ENABLED_AUTHZnorMIGRATE_DISABLED_AUTHZis set, the rule will be skipped, avoiding unnecessary or unforeseen code changes both locally and in the CI.Added fix and test case for
access:${APP.TEST_ID}tags that have property access in the template literal.Closes: #196846
Checklist