-
Notifications
You must be signed in to change notification settings - Fork 81
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
Addresses changes made to security demo config install tool #233
Conversation
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.
@DarshitChanpura , Thank you for making this change.
When will this new password be the default in OpenSearch?
@dlvenable this change will be made in 2.12.0. Also |
@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? |
scripts/docker.env
Outdated
JRUBY_OPTS=-Xregexp.interruptible=true -Xcompile.invokedynamic=true -Xjit.threshold=0 -J-XX:+UseParallelGC -J-XX:+PrintCommandLineFlags -v -W1 | ||
OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123! |
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.
If we change this to admin
, then we can use admin
below and it should work for older versions of OpenSearch. Can we make that change?
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.
Would it work for 2.12 and later? If not and you think this PR is not required until 2.12 we can mark it as draft
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.
Also, admin
is recognized as weak password and so the setup would fail. Hence we defined a new password with relatively strong value myStrongPassword123!
scripts/logstash-run.sh
Outdated
@@ -6,7 +6,7 @@ export PATH=$BUILD_DIR/gradle/bin:$PATH | |||
SERVICE_URL="http://integration:9200" | |||
|
|||
if [[ "$SECURE_INTEGRATION" == "true" ]]; then | |||
SERVICE_URL="https://integration:9200 -k -u admin:admin" | |||
SERVICE_URL="https://integration:9200 -k -u admin:myStrongPassword123!" |
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.
You could set this to admin
to help the build pass.
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.
i don't think that is the root-cause of failures but I maybe wrong here.
In the latest CI run, the test run with logstash 7.17.1 with OpenSearch 2.1.0 seem to have passed[1] but the same failed[2] for 1.3.4, when neither of these versions contain admin changes.
[1] - https://github.com/opensearch-project/logstash-output-opensearch/actions/runs/7227042889/job/19693902342?pr=233
[2] - https://github.com/opensearch-project/logstash-output-opensearch/actions/runs/7227042889/job/19693901900?pr=233
@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: #233 (comment). 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 |
Signed-off-by: Darshit Chanpura <[email protected]>
565a187
to
74328f2
Compare
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. |
80eb3fa
to
07fc6e8
Compare
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.
Thanks for bringing this home @DarshitChanpura
8af1aac
to
bfc0064
Compare
823b7e5
to
14a7cd5
Compare
…rd determination and adds 2.12.0 to CI matrix Signed-off-by: Darshit Chanpura <[email protected]>
14a7cd5
to
81fff85
Compare
@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.