You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, there are two ways http_client sets the authorization (see here):
Default username and password (admin and myStrongPassword123!)
A username and password supplied through CLI (process.env.OPENSEARCH_USERNAME and process.env.OPENSEARCH_PASSWORD)
This will apply to all tests and there is no option to apply it to a specific chapter or test file.
What solution would you like?
This issue requests addition of another way of passing custom authorization headers in request block of chapters. This will then be used by http_client to execute requests. It should look something like this:
DarshitChanpura
changed the title
[FEATURE] Add support for custom authorization headers when running tests.
[FEATURE] Add support for custom authorization headers in chapters section of the tests.
Aug 9, 2024
Is your feature request related to a problem?
As of now, there are two ways http_client sets the authorization (see here):
This will apply to all tests and there is no option to apply it to a specific chapter or test file.
What solution would you like?
This issue requests addition of another way of passing custom authorization headers in
request
block of chapters. This will then be used by http_client to execute requests. It should look something like this:What alternatives have you considered?
NA
Do you have any additional context?
The text was updated successfully, but these errors were encountered: