Invalid config kind for new applicaiton piped v1
Open
Nobody has claimed this yet.
area/pipedv1
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
When new Application for piped v1 created, it is auto setkind = KUBERNETES for all created applications. This led to Invalid config in detail application page as below image.
What you expected to happen:
- Should not showing
invalid config - App created kind should not be fixed to be KUBERNETES
How to reproduce it:
- Create application through application-form-v1 that have
app.pipecd.yamlnot kind KUBERNETES - View detail application page.
- Check for invalid Config message
Environment:
pipedversion: v1.0 testcontrol-planeversion: v0.50.1- Others:
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
Locate the application-form-v1 creation flow and the detail application page, then reproduce the issue with an app.pipecd.yaml whose kind is not KUBERNETES. Trace where the newly created application's kind is assigned and verify the detail page no longer reports Invalid config when the declared kind is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100