add an option to use same headers as metadata service for argo events webhook calls #1560
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oavdeev
force-pushed
the
auth-key-argo-events
branch
3 times, most recently
from
40deea1
to
befd0fe
Compare
oavdeev
changed the title
savingoyal
previously approved these changes
Sep 29, 2023
oavdeev
force-pushed
the
auth-key-argo-events
branch
from
befd0fe
to
eb34cc2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If METAFLOW_ARGO_EVENTS_WEBHOOK_AUTH = service, Metaflow will use same HTTP headers for argo events webhook as for metadata service, including auth. If not set, or set to none the behavior is the same as before