Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix for correctly handling AWS Secrets #2567

Merged
merged 2 commits into from
Nov 5, 2024
Merged

Conversation

mlodic
Copy link
Member

@mlodic mlodic commented Nov 5, 2024

for @drosetti : I added a boolean environment variable for the integration with Elastic to avoid to have empty ("None") environment variables. This would have created problems in case the AWS_SECRETS variable was enabled.

More generally, it would also make more sense to have that boolean flag to enable/disable the feature instead of leveraging an URL-based variable. In this way you don't have to configure the URL multiple times in case of changes but you have to configure a more easily understandable boolean flag.

I updated the doc too: intelowlproject/docs@ecb7c72

@mlodic mlodic requested a review from drosetti November 5, 2024 13:03
@mlodic
Copy link
Member Author

mlodic commented Nov 5, 2024

I am early merging it to enable the user here to solve their problem. In case, please feel free to suggest any changes even afterwards

@mlodic mlodic merged commit 5bcfc89 into develop Nov 5, 2024
12 checks passed
@mlodic mlodic deleted the fix_env_for_aws_secrets branch November 5, 2024 13:20
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant