Assigned
Status Update
No update yet.
Comments
ba...@google.com
ku...@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
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
Since 2nd gen Cloud Functions create a Cloud Run revision on deployment, they should support tagging and naming revisions.
When 2nd gen Cloud Functions are deployed via the
gcloudcommand they do not support the--tagnor--revision-suffixarguments, despite the fact that a Cloud Run revision is automatically created with the deployment. If I want a tagged or custom-named revision then I must redeploy the image for my Cloud Function via Cloud Run.