Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Problem you have encountered: When automatic updates are enabled for Cloud Run functions, the function's runtime image are automatically replaced with a newer revision. This updated revision can be seen function's runtime logs. While the runtime_version is visible in the logs for 1st gen Cloud Run functions, it's not present in the logs for 2nd gen functions, as shown in the screenshot. This doesn't seem like expected behavior.https://cloud.google.com/functions/docs/securing/execution-environment-security#identify_the_runtime_image_used_after_an_automatic_update
What you expected to happen: runtime_version should be present in the Cloud Run Functions gen2 similar to gen1.
Steps to reproduce: Deploy Cloud Run Functions gen1 and gen2 functions compare logs. Look for logs field
Other information (workarounds you have tried, documentation consulted, etc): N/A