-
Notifications
You must be signed in to change notification settings - Fork 114
Remove references to default admin creds #430
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,7 +25,7 @@ printf "Waiting for clusters to get ready " | |
| ALL_CLUSTERS_READY=false | ||
|
|
||
| while ! $ALL_CLUSTERS_READY; do | ||
| (curl -ks -u admin:admin https://localhost:9200 -o /dev/null && curl -ks -u admin:admin https://localhost:9201 -o /dev/null && ALL_CLUSTERS_READY=true) || (printf "." && sleep 5) | ||
| (curl -ks -u admin:myStrongPassword123! https://localhost:9200 -o /dev/null && curl -ks -u admin:admin https://localhost:9201 -o /dev/null && ALL_CLUSTERS_READY=true) || (printf "." && sleep 5) | ||
|
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure where the second cluster is coming from, I think the first cluster is coming from
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can maintainers help out here in understanding if the second cluster needs similar changes/where those that cluster's password should be set?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I do not believe this script is being used anymore. @gkamat can you confirm?
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| done | ||
|
|
||
| echo | ||
|
|
@@ -50,7 +50,7 @@ curl -o /dev/null -H 'Content-Type: application/json' -k -u admin:admin -X PUT h | |
| EOF | ||
|
|
||
| echo "Set auto-follow pattern on follower for every index on leader" | ||
| curl -H 'Content-Type: application/json' -k -u admin:admin https://localhost:9201/_plugins/_replication/_autofollow -d @- <<-EOF | ||
| curl -H 'Content-Type: application/json' -k -u admin:myStrongPassword123! https://localhost:9201/_plugins/_replication/_autofollow -d @- <<-EOF | ||
| { | ||
| "leader_alias": "source", | ||
| "name": "all", | ||
|
|
@@ -90,7 +90,7 @@ cat >ccr-client-options.json <<'EOF' | |
| "default": { | ||
| "use_ssl":"true", | ||
| "basic_auth_user":"admin", | ||
| "basic_auth_password":"admin", | ||
| "basic_auth_password":"myStrongPassword123!", | ||
| "verify_certs":"false" | ||
| }, | ||
| "follower": { | ||
|
|
||
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.
This command would fail if os_version < 2.12.0. Not sure how this file is used/how we can conditionally switch this password. Can maintainers help out here?
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.
@derek-ho Off the top of my head, there's a couple ways that we could get around this. Others might have better ideas
os_versionvariable that's being passed through and if it's < 2.12.0, useadmin. You'll need to make that additional check in this section of provisioner.py and this section of docker_installer.pyyqhttps://stackoverflow.com/questions/76526508/replace-a-block-of-yaml but that would require upkeep with this library and adding it insetup.py