Add support for more `configmap` setup
Open
Nobody has claimed this yet.
area/roadmap
kind/feature
- Dominant language
- Shell
- Stars
- 8
- Forks
- 7
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 1
Description
Today, we can pass, as a json, the featureflag configmap. We should add support for more (the default one, …) but most likely not in the form of json.
See https://github.com/tektoncd/actions/pull/1#discussion_r1505902732
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
The issue names no files, tests, or entry points. Start by reading the linked pull-request discussion, then trace how the action currently accepts the featureflag configmap as JSON. Done means supporting the default configmap and additional configmaps in an agreed non-JSON form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100