[semver:minor] Always allow platform-version overrides #122
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.
Resolves #121
Change the default value for the
platform-version
command/job parameter fromLATEST
to''
, and only provide the--platform-version
argument to the AWS CLI whenplatform-version
is non-blank.The AWS CLI docs for
--platform-version
(https://docs.aws.amazon.com/cli/latest/reference/ecs/run-task.html) state:Hence, this PR should generally be a backwards-compatible change since the AWS CLI already uses
LATEST
as the default when no--platform-version
argument is provided to the CLI anyway, so not passing--platform-version
(which will be the new orb default behavior) should have the same effect as explicitly setting--platform-version LATEST
when the launch type isFARGATE
, as the orb would do in the past.