-
Notifications
You must be signed in to change notification settings - Fork 186
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
Pass in initial admin password and remove admin:admin references #631
Changes from 14 commits
5a70790
065e1bc
b91a8ec
db0e15a
50970d8
02a0d70
8d6fcbb
9d2c999
05eaded
7892fdc
2639850
85b923c
38a676f
cf5602f
ac76aae
e5cd848
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 |
---|---|---|
|
@@ -39,6 +39,7 @@ docker run \ | |
--env "PYTHON_CONNECTION_CLASS=${PYTHON_CONNECTION_CLASS}" \ | ||
--env "TEST_TYPE=server" \ | ||
--env "TEST_PATTERN=${TEST_PATTERN}" \ | ||
--env "OPENSEARCH_INITIAL_ADMIN_PASSWORD=myStrongPassword123!" \ | ||
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. You could avoid the entire if, versions < 2.12 don't care if you set this. 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. Yea, we can skip it but I was having trouble reading the env correctly within the testing code itself to determine which credentials to use when setting up the connection. It seems that I needed to set the env. in the sh file right before the tests ran for it to work. Not sure if there is a simpler way. |
||
--name opensearch-py \ | ||
--rm \ | ||
opensearch-project/opensearch-py \ | ||
|
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 won't work for 2.13, will it?
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.
It should since admin credentials changes were released in 2.12. If you are referencing script execution in general, it works as expected returning
admin:admin
for versions <2.12 andadmin:myStronPassword123!
for those >= 2.12There 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.
Ok, but wouldn't it be simpler to just set
OPENSEARCH_USERNAME
andOPENSEARCH_PASSWORD
inenv:
in the workflow?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.
yes, it should be, however on line 64 we make a status check call that would require the correct credentials to be passed.