-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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: remove squash on configtls.TLSClientSetting for AWS components #5454
fix: remove squash on configtls.TLSClientSetting for AWS components #5454
Conversation
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.
Consider to split into a PR that fixes the broken readmes and other that change the other components to not squash
@bogdandrutu I split them into the first two commits in this PR. |
…ontrib into remove_squash_configtls
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.
See #5466 (review)
…ontrib into remove_squash_configtls
Consider to split per component: splunk/observiq/elastic/aws, since this has approver from aws owners this may contain the aws changes, and create other 3 PRs. We need component owners to ack these changes. |
…ontrib into remove_squash_configtls
Description:
This PR removes squash on
configtls.TLSClientSetting
and update corresponding yaml files to ensure that the unit test passed.Link to tracking Issue:
#5433