-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[provider/googlesecretmanagerprovider] mark the component "Alpha" Stability #39956
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
Conversation
Now that this component exists, please ensure to follow the PR title guidelines. |
@@ -0,0 +1,16 @@ | |||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | |||
change_type: enhancement |
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.
Other alpha component changelogs seem to use new_component
so we should use that here too I think.
change_type: enhancement | |
change_type: new_component |
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.
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.
If the changelog from the previous PR is new_component
then we can leave this one as enhancement.
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.
49a05ab#diff-824a70bad7774ba59c7f93d6564ad3810cf905250bba9c63c1f7577e9bf6dac5R2 If you are referring to this PR, then yes.
reports/distributions/contrib.yaml
Outdated
@@ -118,6 +118,7 @@ components: | |||
- transform | |||
provider: | |||
- aes | |||
- googlesecretmanagerprovider |
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.
This has made me realize that in the initial PR I didn't notice provider
is in the type
field for metadata.yaml
of this component. I don't think it should, as other components of any type don't include the type of component in the type name. So we should change that to googlesecretmanager
along with any other necessary changes from that
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.
Done
…bility (open-telemetry#39956) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description The full implementation of the component is added in : open-telemetry#39790. This PR marks the component "alpha" stability compliant. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#39665 <!--Describe what testing was performed and which tests were added.--> #### Testing [Unit tests](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/confmap/provider/googlesecretmanagerprovider/provider_test.go) <!--Describe the documentation added.--> #### Documentation [README](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/confmap/provider/googlesecretmanagerprovider/README.md) <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Braydon Kains <[email protected]>
Description
The full implementation of the component is added in : #39790.
This PR marks the component "alpha" stability compliant.
Link to tracking issue
#39665
Testing
Unit tests
Documentation
README