fix(functions): update function when runtime has changed and redeploy #3011
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello 👋
Just a small fix 🐛
When a function
runtime
is updated from Terraform:runtime
field was actually not updated (e.g. when weGET
from the API): this is because this case is simply not handled in the existing codedeploy
isfalse
, I think most users expect their function to be rebuilt with the new runtime (e.g. when bumping frompython310
topython313
)If 2. is controversial, maybe we can just replace:
So, runtime is changed, but function is not redeployed unless explicitly told to do so.
Tests
main.tf
:functions/handler.py
:Run
terraform apply
✔️Then, change in
main.tf
:Running
terraform apply
redeploys the function ✔️ (we can check the version has changed by calling the function endpoint).Thanks!