Remove serverless credentials reset #2307
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are using the internal
_reset-internal-credentials
API to obtain the credentials used for serverless stacks managed byelastic-package
. But this API is only available to elastic employees.There were two reasons to obtain credentials this way:
_cluster/health
). In this case, if normal credentials are used, it returns HTTP status 410 (Gone) if the cluster is alive and the credentials are valid, I think we can consider this as an OK for this case. This will be also needed in any case for API keys support, because API keys don't have access to these internal APIs.elastic-package
operations.As these reasons are not strong enough now, I think it would be better if we just avoid these resets.
Relates to #1633, where it was observed that we need to make
elastic-package
work with non-internal credentials.