Skip to content

Conversation

@vikasperi
Copy link
Contributor

Failed instance is resulting in fail of the workflow.

The result of job should not be decided based on the failed count but on the codeDeploy status.

Hence removing the exit when failed instance count is over zero

Copy link
Member

@iBotPeaches iBotPeaches left a comment

Choose a reason for hiding this comment

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

This would be a breaking change as this action for years has always quit when a single instance is marked as failed. So for this to go forward it would need to become a parameter that defaults to the existing behavior.

Could you also describe your use-case that you have a failed instance during deployment, but want to continue polling? I'm just not following why that would occur.

@iBotPeaches iBotPeaches marked this pull request as draft July 10, 2025 21:08
@iBotPeaches
Copy link
Member

Closing for no response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants