feat: write publishing timestamps to SSM #1773
Conversation
Add a feature to allow publishing the latest published version and its timestamp to SSM, so that we can start tracking how long it takes to replicate, and alarm at a different severity if a canary fails and we recently released.
Signed-off-by: github-actions <[email protected]>
There was a problem hiding this comment.
Can't we have this script in a single place?
There was a problem hiding this comment.
Not trivially -- the way the assets are packed means it just uses the specific publishing directory.
We could go for a build step to copy a bunch of files into a specific directory, but since bash doesn't have a way to find or specify directories, it would all be quite magical. The publishing scripts would invoke another script that's not there from the PoV of the calling script (but will be there at runtime because it will have been copied).
If you have a good idea I'm all ears
There was a problem hiding this comment.
Ah, I see the problem. Would it make sense to at least have a build step to make sure they are all identical?
There was a problem hiding this comment.
Yeah I can do that.
…aws-delivlib into huijbers/publish-ssm-timestamps
Add a feature to allow publishing the latest published version and its timestamp to SSM, so that we can start tracking how long it takes to replicate, and alarm at a different severity if a canary fails and we recently released.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.