Assigned
Status Update
No update yet.
Comments
va...@google.com
sa...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the Issue Tracker providing a detailed description of your issue.
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
Objective: We are working on creating a 2nd Generation Cloud Function using Python, deployed via Terraform. The deployment process involves using a GCP Source Repository to store the source and module files, with Cloud Build handling the deployment. The deployment flow includes the creation of a Cloud Storage bucket where the source script is uploaded, and the Cloud Function is then created using this script.
Issue: When the Cloud Function is created, a new bucket is automatically generated with a name following the pattern "gcf-v2-sources-<number>-<region>", and the source script is uploaded there. Upon making updates to the script and redeploying via Cloud Build, the script is correctly updated in the original bucket created during the first deployment. However, the Cloud Function continues to reference the script from the auto-generated bucket, and as a result, it does not recognize the updated script.
Proposed Solution: We would like the Cloud Function to automatically detect and reference the updated script from the original source repository or the Cloud Storage bucket used during the initial deployment when redeploying via Cloud Build with updated scripts.
If applicable, reasons why alternative solutions are not sufficient: No alternate method available.
Other information (workarounds you have tried, documentation consulted, etc):