Can someone confirm this?
If you make a Script Task
And in the script use the aws ssm send-command --instance-ids "<id>"
Make sure it passes when you run the plan.
Now go and change the Name of the Script Task to "NUnit Runner"
When you run the plan again you will receive this error:
Parameter validation failed:
Invalid length for parameter InstanceIds, value: 19, valid range: 10-10
Once the Script fails on this error. It will continually fail no matter what you name it. You must remove the send-command or create a new script.
I think it is a bug.
I found a post that may explain this behavior, however, it's interesting this only happens if you rename the task.
If you run the same command from terminal do you get the same behavior? In case the instance id is causing the problem it would happen in the terminal too.
Let me know and we'll go from there.
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events