Skip to content

Conversation

@feiyangliu2023
Copy link
Contributor

@feiyangliu2023 feiyangliu2023 commented Sep 29, 2025

Issue #, if available:
Currently, update automation action only reports metrics when the action fails. However, in order to monitor if scheduled update is in place, there needs to be metrics sent to cloudwatch, no matter if the action successes or fails.

Description of changes:
This PR refactored execution metrics reporting to dynamically handle success and failure cases

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@feiyangliu2023 feiyangliu2023 had a problem deploying to security-scanning-workflow-env September 29, 2025 14:21 — with GitHub Actions Failure
@feiyangliu2023 feiyangliu2023 had a problem deploying to security-scanning-workflow-env September 29, 2025 14:21 — with GitHub Actions Failure
@feiyangliu2023 feiyangliu2023 marked this pull request as ready for review September 30, 2025 09:27
@feiyangliu2023 feiyangliu2023 requested a review from a team as a code owner September 30, 2025 09:27
@feiyangliu2023 feiyangliu2023 had a problem deploying to security-scanning-workflow-env September 30, 2025 11:34 — with GitHub Actions Failure
@feiyangliu2023 feiyangliu2023 had a problem deploying to security-scanning-workflow-env September 30, 2025 11:34 — with GitHub Actions Failure
@feiyangliu2023 feiyangliu2023 had a problem deploying to security-scanning-workflow-env September 30, 2025 13:25 — with GitHub Actions Failure
@feiyangliu2023 feiyangliu2023 had a problem deploying to security-scanning-workflow-env September 30, 2025 13:25 — with GitHub Actions Failure
needs: [update-automation, build-and-update-package-locks, generate-oss-attribution, create-pr, send-notification]
environment: update-automation-workflow-env
if: success()
if: always() && !failure() && !cancelled()
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice catch adding the !cancelled(). It looks like this will work, but the always() seems redundant, because afaik it always resolves to true (ie: <true> && <true|false> && <true|false> )

@feiyangliu2023 feiyangliu2023 merged commit 2d16366 into aws:main Sep 30, 2025
3 of 6 checks passed
@feiyangliu2023 feiyangliu2023 deleted the add-alarm-test branch October 15, 2025 12:23
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.

3 participants