Float and bool values are changed to int

[Mistic92]

What happened?

In Pulumi.develop.yaml I have values like below

  cloud_run:APP_USE_PPROF: "false"
  cloud_run:APP_TRACE_SAMPLING_RATE: "0.01"

In Pulumi.yaml I'm using them in GCP Cloud Run service

      containers:
          - envs:
              - name: APP_TRACE_SAMPLING_RATE
                value: ${cloud_run:APP_TRACE_SAMPLING_RATE}
              - name: APP_USE_PPROF
                value: ${cloud_run:APP_USE_PPROF}

When I do pulumi up float values are converted to int so my 0.01 is 0.
I found out that using , instead of . does not change value so 0,01 give 0,01 but my app won't handle that.

Also bool values are converted from false/true to 0/1.

Expected Behavior

Support float and don't change bool to int.

Steps to reproduce

Use Pulumi YAML with GCP Cloud Run service.

Output of pulumi about

╰─ pulumi about                                                                                                                                                                                                                            ─╯
CLI          
Version      3.64.0
Go Version   go1.20.3
Go Compiler  gc

Plugins
NAME  VERSION
yaml  unknown

Host     
OS       ubuntu
Version  20.04
Arch     x86_64

This project is written in yaml

Current Stack: XXXXXXXX/usage-reporter/develop

TYPE                                URN
pulumi:pulumi:Stack                 urn:pulumi:develop::usage-reporter::pulumi:pulumi:Stack::usage-reporter-develop
pulumi:providers:gcp                urn:pulumi:develop::usage-reporter::pulumi:providers:gcp::default
gcp:serviceAccount/account:Account  urn:pulumi:develop::usage-reporter::gcp:serviceAccount/account:Account::usagereporter-sa-svc
gcp:cloudrun/service:Service        urn:pulumi:develop::usage-reporter::gcp:cloudrun/service:Service::usagereporter-cloudrun-svc
gcp:cloudrun/iamBinding:IamBinding  urn:pulumi:develop::usage-reporter::gcp:cloudrun/iamBinding:IamBinding::usagereporter-sa-binding


Found no pending operations associated with XXXXXXXX/develop

Backend        
Name           pulumi.com
URL            https://app.pulumi.com/lbyjos
User           lbyjos
Organizations  lbyjos, XXXXXXXX

No dependencies found

Pulumi locates its logs in /tmp by default

Additional context

No response

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).

[Mistic92]

After manual edit of Cloud Run service in GCP Console, refresh I'm doing pulumi up and it tries to change this values again.

          ~ spec    : {
              ~ containers: [
                  ~ [0]: {
                          ~ envs: [
                              ~ [1]: {
                                      + name : "APP_TRACE_SAMPLING_RATE"
                                      + value: 0
                                    }
                              ~ [3]: {
                                      - name : "APP_TRACE_SAMPLING_RATE"
                                      - value: "0.01"
                                    }
                              ~ [7]: {
                                      ~ name : "APP_USE_PPROF" => "APP_USE_PPROF"
                                      ~ value: "false" => false
                                    }
                            ]
                        }
                ]
            }
        }

After accepting changes APP_USE_PPROF is changed to 0...

[jamest-gaia]

Not sure if this is the same or different to #453

[aq17]

@Mistic92 curious if you're using project level configuration? If so, you should be able to declare the desired type of your config values

[jamest-gaia]

@aq17 I don't know whether the OP was, but I already tried that (see #453) and it makes no difference. The only thing that worked for me was defining the values like this

cloud_run:APP_USE_PPROF: |-
  "false"
cloud_run:APP_TRACE_SAMPLING_RATE: |-
  "0.01"

which seems to force Pulumi to treat them as strings. I don't know if this trick would work for the OP though, since my problem was slightly different - I was trying to define values in the config, and pulumi was converting them into types like boolean and integer, when the provider actually wanted strings.

[Mistic92]

We are using stack configuration scope. We have moved back to Go as after 3 weeks there was no update on this bug. Maybe we'll try again to use yaml in the future.

[jamest-pin]

I'm now having this problem again but (sort of) in reverse. I have values I need to be bool but they're being converted to strings. I tried all the same tricks as above. Very frustrating.