This message was deleted.
# general
s
This message was deleted.
b
Hi @sticky-receptionist-53934
My apologies for this - we had a report of this last night (very late) and are looking into the issue
It was certainly not an expected breakage
👍 1
c
Disappointed to find another breaking change make it into pulumi.
Why wasn’t this version pulled or a notice put up with a warning or basically anything given that this has been an issue for at least 8 hours?
b
Hi all We must apologise for the breaking change that occured in the minor version bump of the GCP provider. v3.19.0 introduced a codegen change that ensured consistent package names. This changed the following package names: Go
serviceAccount -> serviceaccount
NodeJS
serviceAccount -> serviceaccount
Python
service_account -> serviceaccount
This was an unintended consequence of the codegen change being released and is something that we should have ensured happened in a controlled manner rather than forcing the breakage on the customer We are going to have a followup post-mortem event to ensure we learn from this and that we add better quality bars to our releases so that we don't release these breaking changes without any warning or notice. We will publish the results of this post-mortem to make sure our customers understand what we have learned from this I am sorry for this issue. If this issue will cause you any unnecessary replacement of any infrastructure, then please do let us know and we can work with you on making sure this isn't the case Paul
👍 1
s
I am still confused, is this change intended or are you going to roll back ?
b
Hi @sticky-receptionist-53934 we feel to roll back would be another breaking change for those that fixed their code already so we’ve made the notice in the changelog what this breaking change has introduced for users to hopefully roll forward I’m sorry I wasn’t so clear above