-
Notifications
You must be signed in to change notification settings - Fork 613
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
EFSVolumeConfiguration -> efsVolumeConfiguration #2254
Conversation
Can you build a test agent image, test against gamma endpoint and include the result in the pr description? Just to double check. |
agent/acs/model/ecsacs/api.go
Outdated
@@ -413,7 +413,7 @@ func (s ECRAuthData) GoString() string { | |||
return s.String() | |||
} | |||
|
|||
type EFSVolumeConfiguration struct { | |||
type EfsVolumeConfiguration struct { |
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.
Did you use gogenerate to generate the api.go file or the command included in the generate.go file? That should be the right way to do it. And if you did that, the struct name should still beEFSVolumeConfiguration.
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.
Approved if I can see some test output, namely the results of all the fun new tests you added:
TestMarshalTaskVolumesEFS
TestUnmarshalTaskVolumesEFS
TestPostUnmarshalTaskWithEFSVolumes
sure....although it's nothing too exciting: % /usr/local/go/bin/go test -count=1 -v -cover -tags unit -timeout=60s -run=arshalTaskVolumes ./agent/api/task/... |
* EFSVolumeConfiguration -> efsVolumeConfiguration * Fix FileSystemId and write json marshalling unit tests * unit test PostUnmarshalTask efsVolumeConfiguration behavior * windows unit test fix
* EFSVolumeConfiguration -> efsVolumeConfiguration * Fix FileSystemId and write json marshalling unit tests * unit test PostUnmarshalTask efsVolumeConfiguration behavior * windows unit test fix
* EFSVolumeConfiguration -> efsVolumeConfiguration * Fix FileSystemId and write json marshalling unit tests * unit test PostUnmarshalTask efsVolumeConfiguration behavior * windows unit test fix
* Added EFSVolumeConfiguration (#2234) * Added EFSVolumeConfiguration models * Translate EFS volumes from ACS to Docker volume type * fix gocyclo failure * code review comments * remove readonly config * remove readonly options from code * code review comments * code review * naming is hard * Add efs capability (#2248) * EFS functional testing (#2247) * Add efs client to Gopkg.* * Add efs client to vendor directory * EFS functional test * Reuse EFS filesystem and mount target(s) * review fixups * more code review fixups * EFSVolumeConfiguration -> efsVolumeConfiguration (#2254) * EFSVolumeConfiguration -> efsVolumeConfiguration * Fix FileSystemId and write json marshalling unit tests * unit test PostUnmarshalTask efsVolumeConfiguration behavior * windows unit test fix * Update ECS client and task defs (#2256) * add memoryUnbounded to task volume marshal unit tests * rebase mistake
Summary
For API consistency this structure has been named efsVolumeConfiguration instead of the originally-planned EFSVolumeConfiguration
Implementation details
Testing
New tests cover the changes: no
Description for the changelog
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.