-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow sprig expressions in WorkflowEventBinding submit metadata #5351
Labels
type/feature
Feature request
Comments
Would you like to submit a PR? You'd need to make changes:
Similar to: https://github.com/argoproj/argo-workflows/blob/master/util/template/template.go#L34 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
#4640 added support for expressions in the name of webhook-submitted workflows. Please allow sprig functions as well.
Use Cases
We're in the same boat as @michaeljohnalbers . We're using Bitbucket Server Webhooks to trigger generic build pipelines in Argo Workflows. Multiple services (repos) are handled by the same WorkflowTemplate. When submitting new Workflows, we'd like to see the actual service being built as part of the name of the workflow.
It seems that only 'simple' expressions are allowed right now, eg. things coming directly from the event payload or metadata. We're having a hard time getting the right naming scheme, because it has to be unique and we're limited to the Kubernetes DNS naming scheme (so it can't be too long).
We have no control over the information coming from Bitbucket Server. Ideally, we'd like to add the commit hash, but the payload only contains the full SHA256 hash, which is too long when combined with the service name. Also, there's no unix timestamp in either the headers or the payload we can use.
If we could do something like this:
it would be absolutely awesome.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: