Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,432
Community Members
 
Community Events
176
Community Groups

Using ssm send-command with a Script named "NUnit Runner" throws error

Edited

Can someone confirm this?

If you make a Script Task

  • Name it "Run Test"
  • Any interpreter
  • inline

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[0], 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.

 

1 answer

0 votes

Hi Jeremy,

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.

Cheers,

Branden

I do not seem to have any issues running it in cmd or powershell. But if my credentials are not set correctly, then it does throw an error on that instance-id.

EDIT: Not the same Parameter error though.

I'll try to reproduce and map my exact steps.

Thanks Jeremy.  Let me know the exact steps and we'll go from there.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events