Deploy a placeholder zip when creating lambda resources#138
Merged
Conversation
We should not be deploying via terraform. It's possible that unreviewed or out of date code may be deployed unintentionally this way. We have a working CI/CD pipeline to deploy lambda code so disable terraform deployment of lambda code in favour of deploying a placeholder zip. This will need to be followed by a CI/CD run but we have a manual trigger in GH Actions to allow us to do this.
cameronhargreaves1-nhs
approved these changes
Jun 17, 2025
Contributor
cameronhargreaves1-nhs
left a comment
cameronhargreaves1-nhs
left a comment
There was a problem hiding this comment.
looks good - cleans the terraform up a lot too!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
We should not be deploying via terraform.
It's possible that unreviewed or out of date code may be deployed unintentionally this way.
We have a working CI/CD pipeline to deploy lambda code so disable terraform deployment of lambda code in favour of deploying a placeholder zip.
This will need to be followed by a CI/CD run but we have a manual trigger in GH Actions to allow us to do this.
Changes
Disable deployment of lambda code via
terraform apply