Hi, I found quite big flaw in

pulumi config set

command (for v1.14.0) when i tried to set value for structured configuration. When I run:

pulumi config set --path key.prop "1002000"

Result is

proj:key:
    prop: 1.002e+06

but for:

pulumi config set --path key.prop "100200"

proj:key:
    prop: 100200

Some one encountered this issue? Independently from this bug it would be nice to force save as text because it impacts program flow.

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)

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

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