You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful to be able to update the images if there are multiple containers in the same task definition. Currently, a user would have to chain multiple of these actions, creating multiple temp files with the iterative changes.
The text was updated successfully, but these errors were encountered:
Just a though - support for updating multiple containers sounds like a bigger change and personally. What if we could try to make chaining multiple update actions easier? This could keep this action small and simple.
If passing the output file between each update action is what makes it hard, maybe the ability to work on the same file will solve this pain point?
I see two options:
Adding a flag overwriting the input file
A more flexible option to specify a path to the output file (could be the same as input)
Overwriting the input file would probably be the best if we're thinking about making chaining easier. This way the order of update actions doesn't matter, they can be moved/removed without breaking the rest of the workflow.
It would be helpful to be able to update the images if there are multiple containers in the same task definition. Currently, a user would have to chain multiple of these actions, creating multiple temp files with the iterative changes.
The text was updated successfully, but these errors were encountered: