-
Notifications
You must be signed in to change notification settings - Fork 424
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
Feature request: easy way to use a service’s task role when running a one-off task #1432
Comments
I think it makes total sense to add a |
Would it make sense to run it with the env variable and secrets specified in the manifest for this service as well ? |
I think so, yes. I think that'd be intuitive and useful. |
Thanks for the feedback that makes a lot of sense! |
Sorry I’m not currently using Copilot, as it's not applicable to my current project. So I don't think I can give good feedback on the proposal. At a high level all the approaches look very promising though. Nice work! |
Right now I can see that a service has a task role, but I don’t see a way to programmatically and automatically get the ARN of that role and pass it to
copilot task run
— I need this to be dynamic because it will vary by environment, and I can’t have a manual step of retrieving the ARN.It’d be great if there was a way to associate a one-off task with a service, just as we can currently associate it with an app and/or an environment; if so I think it’d be natural and intuitive that the one-off task would then use the task role of the service.
Alternatively, perhaps the task role ARN could be exported as a CloudFormation output, or put into an SSM param, so that I could retrieve it via a script using the AWS CLI.
(Right now I’m manually specifying a task role for one-off tasks in one of my add-ons, and then putting its ARN into an SSM param. That’s working, but it took me awhile to work it out, and it’s extra “noise” in my add-on template.)
Thank you!
The text was updated successfully, but these errors were encountered: