-
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
difference behavior of {{= workflow.creationTimestamp }}
and {{ workflow.creationTimestamp }}
#6906
Comments
This is because
I'm not sure this is useful to most users. Options:
This is an easy change. |
@alexec Thanks for quick reply! First, Option 2 seems to be good for me, but I'm not sure which is the best option for the future of Argo WF. I prefer option 1 and add some utility function to manipulate a date (like |
@alexec i would be happy to contribute it. can you assign it to me please? |
…roj#7044) Signed-off-by: kriti-sc <kathuriakriti1@gmail.com>
I need this feature also. :) |
Summary
What happened/what you expected to happen?
{{= workflow.creationTimesamp }}
should be rfc3339 string, but outputs a map representation like:some investigations
In Template.Replace,
I guess
simpleReplace
searches flattenedreplaceMap
and good, butexpressionReplace
has a "nested" replaceMap, asenv
,so the key
workflow.creationTimestamp
becomes a map[string]interface{}.I'd like to get a formatted string value or time.Time instance to send sprig.dateModify like:
Or more simply to send to dateModify,
I would appreciate if Argo WF has
workflow.creationTimestamp.time
orasTime(workflow.creationTimestamp)
.What version of Argo Workflows are you running?
v3.1.8
Diagnostics
Either a workflow that reproduces the bug, or paste you whole workflow YAML, including status, something like:
What Kubernetes provider are you using?
Amazon EKS
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: