argoproj / argoproj/argo-workflows
`generateName` or `name` should allow variables in their definition
Open
area/spec
area/templating
solution/workaround
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 138
Description
if I try some variable within these values they complain about `{ is not a valid alphanumeric`
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the validation and parsing paths for workflow `generateName` and `name`, then reproduce the reported error with a variable value. Done means supported variables are accepted in these fields without the alphanumeric validation error, with coverage for the relevant behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100