bitnami / bitnami/sealed-secrets
scope annotation should be `sealedsecrets.bitnami.com/scope`
- Dominant language
- Go
- Stars
- 9.3k
- Forks
- 776
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 30
Description
It doesn't make sense to combine the following annotations:
```
sealedsecrets.bitnami.com/cluster-wide
sealedsecrets.bitnami.com/strict
sealedsecrets.bitnami.com/namespace-wide
```
so the annotation for this should really be:
```
sealedsecrets.bitnami.com/scope
```
with the possible values being `cluster-wide`, `strict`, `namespace-wide`
Contributor guide
Research direction
Start by locating where the sealed-secrets controller handles the cluster-wide, strict, and namespace-wide annotations. Check how those values are documented and tested, then determine whether the proposed scope annotation can replace them consistently. Done means the supported annotation is sealedsecrets.bitnami.com/scope with the three stated values and the old combination is no longer required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100