Problem
When versioning: true is set on a function, the function URL still points to $LATEST. This means every invocation via the URL runs whatever code $LATEST currently holds.
Expected behavior
At minimum, the function URL should be pinned to a specific published version.
Ideally, the function URL should point to an alias. This setup allows you to roll back the version on the alias without modifying the Function URL configuration or the Lambda permission configuration. If the URL points to a specific version, you must update it to make the older version the primary target. With an alias, this is not an issue. You only need to update the version that the alias points to, and requests will start reaching the older version.
Related
This is part of a broader issue: when versioning is enabled, all event sources (not just function URLs) should invoke through an alias rather than $LATEST or a bare version number. See #6722
Problem
When
versioning: trueis set on a function, the function URL still points to$LATEST. This means every invocation via the URL runs whatever code$LATESTcurrently holds.Expected behavior
At minimum, the function URL should be pinned to a specific published version.
Ideally, the function URL should point to an alias. This setup allows you to roll back the version on the alias without modifying the Function URL configuration or the Lambda permission configuration. If the URL points to a specific version, you must update it to make the older version the primary target. With an alias, this is not an issue. You only need to update the version that the alias points to, and requests will start reaching the older version.
Related
This is part of a broader issue: when versioning is enabled, all event sources (not just function URLs) should invoke through an alias rather than
$LATESTor a bare version number. See #6722