Conflict with config canonical form

[squadgazzz]

What happened?

Enabling Server-Side Apply in Pulumi Kubernetes Provider led to a conflict when k8s automatically changes params format.

Example

in the pulumi config, I specified a value for CPU as 1000m where in fact k8s shows it as just 1 which is identical, but pulumi preview/up raises a conflict now since 1 is not equal to 1000m in the string representation manner.

Output of pulumi about

CLI
Version      3.99.0
Go Version   go1.21.5
Go Compiler  gc

Plugins
NAME    VERSION
nodejs  unknown

Host
OS       darwin
Version  14.2.1
Arch     x86_64

Additional context

Is there a simple way to avoid this type of conflict without adjusting the pulumi config manually or creating our own converters? I'd like to keep 1000m explicitly in the config instead of switching to 1.

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).