Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat: Add support for 'VolumeConfigurations' property on both UpdateService and RunTask API call #721
feat: Add support for 'VolumeConfigurations' property on both UpdateService and RunTask API call #721
Changes from 15 commits
47333c8
41cb704
cc490ca
18081f9
60308e8
88cc3e2
0f33b03
d83db92
cabe278
f0981f6
63285fe
0f3d04b
3b1c0ed
07f78f1
0ed20b3
62d2ebc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have we thought about auto populating this property for customers from the
task-definition.json
file provided in the input? Also, would auto-populate break any existing customers or in other words would it be backwards compatible?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, That is a good point. I think it would be possible to auto-populate the volume name from task-definition if, the task-definition contains a volume with
configuredAtLaunch
set totrue
. We could parse the Volume property from a pre-existingTaskDefinitionContents
variable.Backward-compatibility wise - it should be fine, because:
Pros of this auto-population I think would be:
Cons might be: