[chore][receiver/oracledb] Add required permissions to README #32389
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
codeboten
approved these changes
Apr 15, 2024
atoulme
approved these changes
Apr 15, 2024
dmitryax
approved these changes
Apr 16, 2024
rimitchell
pushed a commit
to rimitchell/opentelemetry-collector-contrib
that referenced
this pull request
May 8, 2024
…elemetry#32389) **Description:** An additional permission is now required in some cases of running the Oracle DB receiver, as a result of open-telemetry#32028. We should document it in the README. I also upgraded this change to a breaking change to make it clear to users that new permissions are needed. **Link to tracking Issue:** Resolves open-telemetry#32373
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.
Description:
An additional permission is now required in some cases of running the Oracle DB receiver, as a result of #32028. We should document it in the README.
I also upgraded this change to a breaking change to make it clear to users that new permissions are needed.
Link to tracking Issue:
Resolves #32373