Going from describe_task_definition to register_task_definition #676
Unanswered
canadiannomad
asked this question in
Q&A
Replies: 1 comment 1 reply
-
You're not missing anything. The way ECS is modeled is just not well tailored to this use-case. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I feel like I'm using the SDK in hard mode.. So it is likely just a misunderstanding of mine... Yet I can't find decent documentation on how to do it...
How can I take the output from a "describe" function, modify it, and send it to an update function without going through .every .single.function. of the associated builder?
Currently I have code similar to the following:
When I really feel like I should be able to do something like:
Or more generically I'd love to be able to skip the builder altogether, and send a *Input to the client.. eg:
Then I'd be able to create my own helpers to convert one to the other. (In many cases it is a 1:1 value copy..)
So what is it that I'm missing to be able to do these describe-modify-update type actions using the SDK?
Beta Was this translation helpful? Give feedback.
All reactions