Remove support for passing orgKey as query param, require use of razee-org-key header #1332
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.
Remove support for passing orgKey as query param, require use of razee-org-key header.
This is a breaking change to the
registerCluster
andenableRegistrationUrl
response. Previously theurl
in the response could be used by itself, e.g.kubectl apply -f [url]
. After this change, this will no longer work as theorgKey
will not be part ofurl
and the expectedrazee-org-key
header cannot be passed bykubectl
.Before updating to this version of Razeedash-api, any consumer of the
registerCluster
orenableRegistrationUrl
apis must be updated to support theheaders
response.