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

<@U013Q0AKUCW> yeah, both with ` and " but that adds those quotes and additional ticks around the value which breaks the thing down the line because it tries to find a Docker image `api:\"20220117.1\"`

A stupid hack to get you by for now could be a prefix to coerce it to be a string.  I do believe this is a bug.

there was some regression some time ago regarding config values (something about migrating string values to numbers)

I think it might be related (or at least it sounds like that), let me find the GH issue…

yeah, that involves changing a bunch of pipelines which were happily working for approx a year...

It's probably time to remove the `latest`  value for the Pulumi version, and specify a number there :slightly_smiling_face:

Hmm, I think that was it: <https://github.com/pulumi/pulumi/issues/8752>

It looks like the bug was introduced in 3.22.0 and it was resolved in a patch 3.22.1. <@U016GHB7ZKJ> can you check what version was used in your case?

<@U0288KYUB7C> thank you so much - I have it set to `latest` and it's using `3.22.0` :slightly_smiling_face:
Let me manually set it to either `3.22.1` or something older

<https://github.com/pulumi/pulumi/issues/8752> was the problem, <https://www.pulumi.com/latest-version> is out of date and isn't reporting the patch version of 3.22.1 but if you manually update to that (or wait a bit, we're currently fixing it to not be out of date) it should stop breaking the config files

thanks <@U02J3T6A8LB>
I've updated the version to 3.22.1 and I'm waiting to see if everything works :slightly_smiling_face: