This message was deleted.
# pulumi-cloud
s
This message was deleted.
m
Interesting, let me check with engineering.
1
Is it possible to create a support request for this? https://support.pulumi.com/hc/en-us Many thanks Steffen!
m
Hi Engin, I've created a support ticket.
m
Many thanks Steffen!
Hi Steffen, I just saw that I send you the link to a GH issue in a private repository. Sorry for that. I will let you know on any changes about this. Hopefully later, when the US based engineers are online! Engin
m
Yeah, I noticed that I could not see the issue 😉. Thanks for keeping me updated and enjoy your weekend.
m
I moved the issue as it is an automation issue and not service-> https://github.com/pulumi/pulumi/issues/11518 Have a nice weekend too Steffen!
Hi @magnificent-scientist-64889, https://github.com/pulumi/pulumi/issues/11518 blocking you right now?
m
I've worked around it in our specific use case, so for now it isn't blocking - but it's not pretty either and this is still a thing that could give potential headaches down the line. The workaround plays on how the config is loaded, so we can set the
aws:allowedAccountIds
by doing
JSON.stringify(['012345678912'])
. This only works for objects.
👀 1
FYI - just posted the full example of the work around in the issue, so others who might stumble upon it, until it's fixed, has a way around it.
👍 1