Relax name validation in chef-server
Open
Nobody has claimed this yet.
Aspect: Portability
Aspect: UX
Component: opscode-erchef
Component: others
Status: Consider for next release
Triage: Confirmed
Type: Enhancement
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Many objects in chef-server have stricter naming validation than our users may like. In many cases this doesn't feel strictly necessary. While we do need many names to be rendered into URIs, we could use percent escaping to make more complex names URI-safe.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the name-validation paths for the objects handled by chef-server and the URI rendering paths they feed. Define which names should be accepted and how percent escaping would preserve URI safety; the work is done when the agreed cases are supported consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100