[aws_logs] Enable secret variable for aws_logs integration

[kaiyan-sheng]

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

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

[gizas]

Also kibana version should be ^8.12.0, see #9022

[kaiyan-sheng]

@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!

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 05ed7cc

History

• 💚 Build #9118 succeeded 80236a3
• 💔 Build #9112 failed 044736e
• 💚 Build #8498 succeeded 2958461

cc @kaiyan-sheng

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[vigneshshanmugam]

LGTM

[elasticmachine]

Package aws_logs - 1.1.0 containing this change is available at https://epr.elastic.co/search?package=aws_logs