Azure / Azure/azure-workload-identity
Generating generic patches for only the required changes
Open
enhancement
- Dominant language
- Go
- Stars
- 337
- Forks
- 122
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 3
Description
ref: https://github.com/Azure/azure-workload-identity/issues/1312
How can we better handle the scenario in future when new fields are added to the pod spec and ensure the webhook isn't dropping fields that it doesn't know about?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked issue 1312 and tracing the webhook's handling of pod-spec fields. Define how generic patches should include only required changes while preserving fields the webhook does not know about; done means newly added pod-spec fields are not dropped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- authentication, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100