Closed DarshitChanpura closed 7 months ago
@dlvenable this change will be made in 2.12.0. Also myStrongPassword123!
is not the new default - it is set as in the env file of this PR. However, I double checked the CI workflow, and it seems like the latest this repo is running is 2.1.0, so I think this PR is not necessary. Please let me know if you agree - if at some point later on this PR starts running CI with 2.12.0 or onwards, there may be changes needed. Otherwise I will close this out.
@dlvenable @asifsmohammed @oeyh Can we get some reviews on this? Also, as @derek-ho mentioned, if this PR is not required please feel free to close it.
@dlvenable @asifsmohammed @oeyh Can we get some reviews on this?
@dlvenable @oeyh @asifsmohammed Now that 2.12 is released this should be unblocked. Would one of you mind bringing this home?
@DarshitChanpura rebase? Let's see a green CI?
@dblock the branch is already pointing to latest commit on main. The CI failures seem unrelated to the changes in this PR: https://github.com/opensearch-project/logstash-output-opensearch/pull/233#discussion_r1473275849.
Maybe flaky? A retry of CI tasks could help determine if they are indeed flaky. @dlvenable Thoughts?
The run is too old to be retried via the GitHub UX, do a git commit --amend
then force push and it will kick it off.
done.
Not sure if it's related, but spec failures look legit, someone will need to look at those.
@dlvenable @asifsmohammed @oeyh Can one of you help resolve the CI and bring this home?
Edit; looking into CI failures, seems like a version check is required.
@dblock @dlvenable @asifsmohammed @oeyh CI is green now. Mind adding some reviews?
LGTM, I'm not a maintainer, leaving this to others!
Description
There were recent changes to security demo configuration setup which now requires a custom admin Password to be setup. This PR updates the documentation and related code change.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check here.