fix: support camel case for step exit code field #1031
Merged
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.
Summary
Fixes step exit code field to support both camelCase (
exitCode
) and snake_case (exit_code
) formats for consistency with other fields.This is a follow-up to #986 which added support for both formats in
continueOn
fields. The same inconsistency existed for exit code fields in retry and repeat policies.Changes
retryPolicyDef
andrepeatPolicyDef
to acceptany
type for exit code fieldsexitCode
andexit_code
formatsTesting
Tested with both formats: