Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: trigger cold start dispatcher after update SSM parameters #4243

Merged
merged 5 commits into from
Nov 7, 2024

Conversation

npalm
Copy link
Member

@npalm npalm commented Nov 7, 2024

Description

Currently we use the lifecyle trigger in Terraform to enforce lambda reload. Unwanted side-effect is resources getting destroyed. Even leading to the lambda trigger for the dispatch functiong not getting re-created.

Instead of adding the lifecyle event to multiple resources, the version of the SSM paramater is added to environment variables of the Lambda to enforce cold start after updates.

Tested

  • default example
  • multi runner, changing labels

@npalm npalm changed the title fix: trigger cold start dispatcher after update SSM paramates fix: trigger cold start dispatcher after update SSM parameters Nov 7, 2024
Copy link
Member

@Brend-Smits Brend-Smits left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@npalm npalm merged commit 580d24b into main Nov 7, 2024
46 checks passed
@npalm npalm deleted the npalm/lifecycle-dispatcher branch November 7, 2024 17:22
npalm pushed a commit that referenced this pull request Nov 7, 2024
🤖 I have created a release *beep* *boop*
---


##
[5.18.4](v5.18.3...v5.18.4)
(2024-11-07)


### Bug Fixes

* trigger cold start dispatcher after update SSM parameters
([#4243](#4243))
([580d24b](580d24b))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: forest-releaser[bot] <80285352+forest-releaser[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants