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
While trying to connect to Elastic cloud we now have to supply a username and password. Since the Uri parameter can be read from the environment using ${environment:SOME_ENV_HOST} i thought why not do the same with password. However this seems not to work because when sending the /_bulk the decoded auth header is the following: some_user:${environment:SOME_ENV_PASS} this obviously does not authenticate correctly with Elastic cloud resulting in an unauthorized...
The text was updated successfully, but these errors were encountered:
Yes, currently we're only passing in username and password if specified in config. It would make sense to allow environment variables though. Possibly ES_USER, ES_PASSWORD,...
While trying to connect to Elastic cloud we now have to supply a username and password. Since the Uri parameter can be read from the environment using
${environment:SOME_ENV_HOST}
i thought why not do the same with password. However this seems not to work because when sending the/_bulk
the decoded auth header is the following:some_user:${environment:SOME_ENV_PASS}
this obviously does not authenticate correctly with Elastic cloud resulting in an unauthorized...The text was updated successfully, but these errors were encountered: