-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloud Function is not updated when BucketObject changes #370
Comments
I had the same issue. I ended up changing the name of the of the Bucket Object on each deployment. The downside is it deploys a new object with every deployment, whether the function code has changed or not. |
This looks like a bug of the Found out that the classic provider has behavior of replacing the object when content changes, but the native provider does not. Workaround: add |
I am able to repro this and seeing the same thing @lephuongbg mentioned. What's the best way to help resolve this issue? I'm new to the pulumi codebase, but am open to contributing if someone can point me in the right direction. Thanks! |
Not sure if related but I'm seeing a similar with the classic provider. Unlike with this issue, the BucketObject changing does trigger an update of the Function, but after the update the Function is still using the old code. I have been able to fix it by setting |
Also seeing this but that option is not available on Python |
temporary workaround: run |
Additional information. Do not set up the name parameter of a bucket object due to replaceOnChanges will not effect in this case. |
|
Any update on this issue? |
Hello!
Issue details
Changing the code triggers the update for the BucketObject, but the function is not updated as it should be.
Steps to reproduce
My code (bundled):
Any code changes to
![image](https://user-images.githubusercontent.com/18534956/156931075-abf532bf-1fe7-46fa-a6c8-d1d5c7115d03.png)
bundle/asset-callback/index.js
triggers changes on BucketObject but the function don't catch the update:Versions
PS: With the GCP (Classic) provider, I'm getting the correct behavior, and this issue is somehow related to #177
Expected: When the code is updated, the function must be deployed with it's new content from bucket
Actual: The BucketObjcet is updated, but the function keeps the same previous code.
The text was updated successfully, but these errors were encountered: