-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is no way to run a custom shell script with AWS credentials #54
Comments
+1 for this approach, it's consistent with how Microsoft provide an 'Azure PowerShell script' task. |
I like the idea, I'll see what the team can do. |
Any news on whether this is likely to be done @steveataws? This would be a really good enabler for me and my team. |
It's still in the backlog for consideration but hasn't received any attention yet, as we've been focused on updating credentials and region settings to be more flexible. That work is coming to an end so I'll bump this up the list, maybe we can sneak something in before release :-) |
@steveataws That was be fantastic, thank you. Fingers crossed you get time! Any idea when the release can be expected? The credentials and region settings flexibility would also be great. |
I can't give an exact ETA but we hope to release the credential changes in July. That gives us some time to consider what to do about shell scripts too :-) |
Exciting stuff @steveataws! Thanks for the update. |
Resolving, included in v1.1.0 released Aug 2nd. |
This is great @steveataws! Thanks so much for this. |
Motivation: I need to run a hashicorp packer command that makes use of the aws-ebs builder from a private linux agent, using an aws endpoint configured in vsts.
I've tried to use an AWS Powershell Script task, which does not work, since that task is only available for Windows agents (until Powershell.Core support is added, see #53).
I then looked at the AWS Cli task, which does not work, because that task only supports
aws <command> <subcommand>
The big gap in the AWS Tools for Team Services, is (i think) a task like
AWS Shell Script (Run a shell script using bash with aws credentials)
Which would take either a script file name or an inline script.
As a workaround for now, I could configure the aws credentials in the private linux agent statically, and mark that agent with a capability, and use the
Shell Script
task. But that does not feel right, as the agent might be configured by mistake to access a completely different account.I looked at the source code, and must admit, i don't have enough knowledge of node / typescript / vsts-extensions to contribute a PR.
Thoughts?
The text was updated successfully, but these errors were encountered: