mayadata-io / mayadata-io/cstorpoolauto
logic: avoid prefixing to given name to derive a new name if original name is auto generated
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
There are cases, where names of a resource are derived from names of other resources. In such cases, it might be good to avoid prefixing values s.a namespace etc. This helps avoid growing the name to reach their max limit.
In addition, it will be good to verify if entire UID needs to be used while forming a name when the case demands the use of the UID?
Check how to make use of namespace & name of a resource to generate the name of another resource.
e.g. (a-b, c-d) (a-b-c, d) may generate same name of ns-name is used as a format to generate name for a resource.
Contributor guide
No contributing guide indexed for this repository
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 tracing the resource name-generation entry point and how it uses namespace, name, prefixes, and UIDs. Compare the collision example in the issue, then define and test naming behavior that avoids unnecessary prefixes and uses only the UID portion required by the case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100