Open achanda opened 1 year ago
Not all YAML strings must be quoted, anything that can't be interpreted as another type will be unquoted most of the time. Is there a specific error that you're getting when trying to use these outputted manifests?
A quick check of the above manifest looks like all of those parameter values are proper strings.
This seems like an issue the cnpg
operator because the YAML is completely valid, and all parameters are indeed strings.
Having said that, since a user can manually quote (even if to overcome a third-party bug), we should also allow this. Right now i'm not sure its possible.
Description of the bug:
I am using cdk8s using Go to manage CloudnativePG clusters. The generated yaml has some config parameters without quotes.
Reproduction Steps:
This produces the following yaml
Some postgres params are quoted while some are not. This does not work since the cnpg operator expects all params to be strings.
Error Log:
There are no errors
Environment:
OS: MacOS 13.5
This is :bug: Bug Report