-
Notifications
You must be signed in to change notification settings - Fork 1k
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
FIX #17042 - Allow non admin/bot to read profiler global config #18292
Merged
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
…ckage name (i.e. customProperties -- uppercase P)
github-actions
bot
added
Ingestion
safe to test
Add this label to run secure Github workflows on PRs
labels
Oct 16, 2024
Quality Gate passed for 'open-metadata-ingestion'Issues Measures |
harshach
approved these changes
Oct 17, 2024
sushi30
reviewed
Oct 17, 2024
openmetadata-spec/src/main/resources/json/schema/type/customProperties/enumConfig.json
Show resolved
Hide resolved
sushi30
approved these changes
Oct 17, 2024
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.
nit: add reason for changing of customProperties
-> customproperties
so that it we have it in our commit log.
harshach
pushed a commit
that referenced
this pull request
Oct 17, 2024
* fix: custom properties folder name in generation to match expected package name (i.e. customProperties -- uppercase P) * fix: allow non admin/bot to read profiler global config with the right permission * style: ran java linting * fix: custom properties import casing
harshach
pushed a commit
that referenced
this pull request
Oct 19, 2024
* fix: custom properties folder name in generation to match expected package name (i.e. customProperties -- uppercase P) * fix: allow non admin/bot to read profiler global config with the right permission * style: ran java linting * fix: custom properties import casing
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.
Describe your changes:
Fixes #17042
ViewProfilerGlobalConfig
permission to allow non admin/bot to read global profiler config on ingestion when using their personal token --ViewAll
will allow reading this config. It is possible to addViewAll
and explicitly denyViewProfilerGlobalConfig
if one chooses tocustomproperties
tocustomProperties
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>
Bug fix