[confmap] Allow using any type as a string #10800
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Allows any type to be used as a string if the target field is a string or the value is expanded in inline position. Inspired by #10794. This is not a breaking change (previously we would return an error for these).
Some things that you can do after this PR that you couldn't do before it:
HOST
to[2001:db8::8a2e:370:7334]
and use it in an endpoint:Pass really big numbers as strings (e.g.
10000000000000000000
)Pass
null
as a string.Types that can be returned by our current YAML parser
Our current way of using the YAML parser has these types:
string
,nil
,int
,uint64
,float64
,map[any]any
,map[string]any
,[]any
.There is no documentation for this, but the following fuzzing test did not find any failing cases after 20 minutes of continous run: