We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
using the plugin to retrieve secrets with json key:
plugins: - seek-oss/aws-sm#v2.3.2: json-to-env: - json-key: . secret-id: prod/AppBeta/Mysql - json-key: . secret-id: prod/AppBeta/Redpanda
the buildkite log has 2 extra blank lines per secret:
| 2024-07-02 00:46:37 CDT | 🔑 Reading secrets from AWS SM | 2024-07-02 00:46:37 CDT | Reading all environment variables from prod/AppBeta/Mysql in AWS SM | 2024-07-02 00:46:37 CDT | | 2024-07-02 00:46:37 CDT | | 2024-07-02 00:46:37 CDT | Setting environment variable MYSQL_DSN | 2024-07-02 00:46:37 CDT | Reading all environment variables from prod/AppBeta/Redpanda in AWS SM | 2024-07-02 00:46:37 CDT | | 2024-07-02 00:46:38 CDT | | 2024-07-02 00:46:38 CDT | Setting environment variable REDPANDA_USER | 2024-07-02 00:46:38 CDT | Setting environment variable REDPANDA_PASSWORD
removing the blank lines would make it easier for human eyes to associate aws sm secret name with env var name
The text was updated successfully, but these errors were encountered:
PRs welcome!
Sorry, something went wrong.
No branches or pull requests
using the plugin to retrieve secrets with json key:
the buildkite log has 2 extra blank lines per secret:
removing the blank lines would make it easier for human eyes to associate aws sm secret name with env var name
The text was updated successfully, but these errors were encountered: