Ved nytt miljø som ikke er helt "klart enda" funker ikke secret management
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 2
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 17
Description
{"actor":"vegar.sechmann.molvig@nav.no","error":"input: team.secrets listing secrets for environment \"dev\": secrets is forbidden: User \"vegar.sechmann.molvig@nav.no\" cannot list resource \"secrets\" in API group \"\" in the namespace \"nais\"","level":"error","msg":"unhandled error: \"input: team.secrets listing secrets for environment \\\"dev\\\": secrets is forbidden: User \\\"vegar.sechmann.molvig@nav.no\\\" cannot list resource \\\"secrets\\\" in API group \\\"\\\" in the namespace \\\"nais\\\"\"","time":"2024-11-27T09:32:14Z"}
Logges i nais-api, og siden ser sånn ut:
Dette er nok fordi miljøet ikke er reconcila enda, men for å få det til å reconcile måtte vi legge det til i nais-api først. Høna og egget her altså.
Løsning: ikke tryn hele secret management siden om ett miljø feiler.
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 in nais-api's secret management flow and reproduce the error with an environment that has not reconciled yet. Trace how one failing environment affects the page; done means secret management remains usable when an individual environment cannot list its secrets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100