No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

It's setting as a number and the value is the same. For a number property there is no problem as neither yaml nor json differentiate integer from floats, it's all just numbers.

If the intention was to have a string then I agree there could be a `--string` option to the command.

As a possible workaround, could you try piping the value in? Like `echo "1002000" | pulumi config set --path key.prop`

My intention is to set string there and I can't find a way to do it with command (I have a lot stack files to update with script)
&gt; As a possible workaround, could you try piping the value in? Like `echo "1002000" | pulumi config set --path key.prop`
Yes I tried. It behaves the same

<@USC68LB3J> yes, you are right when i get the value in program it's `1002000` . Unfortunately I need string there. Only workaround I can see now is to make some ugly code which handles it.

Related: <https://github.com/pulumi/pulumi/issues/4295>

In the meantime, to workaround you could wrap the value in the yaml file with quotes.