Azure / Azure/bicep-extensibility
Improve handling for 'intorstring' in Kubernetes
- Dominant language
- C#
- Stars
- 19
- Forks
- 15
- Avg merge
- 3h 11m
- Merged PRs (30d)
- 20
Description
Right now an 'intorstring' field gets mapped to Bicep as `string | null` instead of `int | string | null`. Usually for these fields the `int` is the common use case so it can be misleading.
`intorstring` is a special Kuberentes construct for `int | string`.
A good example is `targetPort` in pods.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how Kubernetes `intorstring` fields, using pod `targetPort` as the example, are mapped to Bicep types. Confirm the current mapping produces `string | null`, then verify that the completed change represents the intended `int | string | null` type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, kubernetes
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100