Closed azamat-sharapov closed 2 years ago
I am coming across this problem as well and would love to have either a work around or a fix.
I think this is a general problem with "arguments", I tried to use the --ignore-application-stop-failures
argument, and I get the same error. Looking at the error,
while [[ $STATUS == "Created" || $STATUS == "InProgress" || $STATUS == "Pending" || $STATUS == "Queued" || $STATUS == "Ready" ]]; do
echo "Status: $STATUS..."
STATUS=$(aws deploy get-deployment \
--deployment-id $ID \
--output text \
--query '[deploymentInfo.status]' --ignore-application-stop-failures)
sleep 5
done
it make me wonder if the get-deployment
commnd, needs the arguments field inputs at all?
As a workaround, I copied whole deploy-bundle
command from orb source and edited it manually.
The issue was resolved in the PR #11.
Orb Version
1.0.1
Describe the bug
When you pass
arguments
todeploy-bundle
command, it passes them both foraws deploy create-deployment
andaws deploy get-deployment
, resulting deployment failure, like: Unknown options: --file-exists-behavior=OVERWRITETo Reproduce
Expected behavior
We probably need 2 params for this. One for
create-deployment
subcommand, another forget-deployment
.