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
[aws_logs] Enable secret variable for aws_logs integration #9019
Conversation
Also kibana version should be ^8.12.0, see #9022 |
@gizas Yes I changed the kibana version back because I see some of the integrations are keeping the kibana version "For packages < 8.10.0, retain existing Kibana version. Changelog descriptions for these packages indicate that secrets are supported from version 8.12, allowing users to upgrade stack at their discretion." from #9009. But I think it's better to just bump the version to 8.12.0 anyway and make sure users adopt the secrets and password type. I just made the change in the latest commit. Thanks! |
💚 Build Succeeded
History
|
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
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.
LGTM
Package aws_logs - 1.1.0 containing this change is available at https://epr.elastic.co/search?package=aws_logs |
Proposed commit message
This PR is to enable secrets for identified sensitive fields and update package-spec to 3.0.2 to utilize the validation checks for secrets.
Checklist
changelog.yml
file.