cockroachdb / cockroachdb/cockroach-operator
Check that when user sets custom TLS secrets both are set
Open
- Dominant language
- Go
- Stars
- 318
- Forks
- 104
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 1
Description
We are not checking that both secrets are set and that the secrets exist. Maybe we should check the format of the secrets as well.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is identified. Locate the validation path for custom TLS secrets, then determine how missing pairs, nonexistent secrets, and secret format should be handled; done means these cases are checked with clear validation results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100