argoproj / argoproj/argo-workflows
Support input/output names containing spaces
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
**Is this a BUG REPORT or FEATURE REQUEST?**:
FEATURE REQUEST
Currently, the input/output names cannot have spaces. I see no technical reason for that.
I'd like to be able to use input/output names with spaces.
Maybe this can be extended to template names. (Task names and workflow name probably cannot have spaces since they're used for Kubernetes resource names.)
Contributor guide
Research direction
The issue does not name files, tests, or entry points. Start by locating where input/output names are validated and where workflow templates are represented, then check the Kubernetes naming constraints mentioned in the request. Done means input and output names containing spaces work without breaking task or workflow resource naming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100