We're using `pulumi config set` in a CI/CD pipelin...
# general
c
We're using
pulumi config set
in a CI/CD pipeline to update the tag of the Docker image. The tag format is the build number we're using -
YYYYMMDD.r
where
r
is the build iteration in that day - for example -
20220117.1
The problem is that since a few days ago pulumi CLI started saving the value as
2.02201171e+07
Any idea what to do with this? 😄
m
Have you tried quoting it?
c
@millions-furniture-75402 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\"
🤦‍♂️ 1
m
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.
or change
.
to something else
p
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…
❤️ 1
c
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 🙂
p
It looks like the bug was introduced in 3.22.0 and it was resolved in a patch 3.22.1. @cool-jewelry-33023 can you check what version was used in your case?
❤️ 1
c
@prehistoric-activity-61023 thank you so much - I have it set to
latest
and it's using
3.22.0
🙂 Let me manually set it to either
3.22.1
or something older
e
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
❤️ 1
c
thanks @echoing-dinner-19531 I've updated the version to 3.22.1 and I'm waiting to see if everything works 🙂