deep-stack/kompose
7
0
Fork 0
forked from LaconicNetwork/kompose
Code Pull Requests Activity

Merge pull request #949 from hangyan/fix-broken-links

Browse Source 
Fix broken links for volume long syntax in comments
This commit is contained in:
Suraj Narwade 2018-03-06 14:38:43 +05:30 committed by GitHub
commit 1ec191d654
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pkg/loader/compose/v3.go
View File

@ -121,7 +121,7 @@ func parseV3(files []string) (kobject.KomposeObject, error) {
// Convert the Docker Compose v3 volumes to []string (the old way) // Convert the Docker Compose v3 volumes to []string (the old way)
// TODO: Check to see if it's a "bind" or "volume". Ignore for now. // TODO: Check to see if it's a "bind" or "volume". Ignore for now.
// TODO: Refactor it similar to loadV3Ports // TODO: Refactor it similar to loadV3Ports
// See: https://docs.docker.com/compose/compose-file/#long-syntax-2 // See: https://docs.docker.com/compose/compose-file/#long-syntax-3
func loadV3Volumes(volumes []types.ServiceVolumeConfig) []string { func loadV3Volumes(volumes []types.ServiceVolumeConfig) []string {
var volArray []string var volArray []string
for _, vol := range volumes { for _, vol := range volumes {
@ -345,7 +345,7 @@ func dockerComposeToKomposeMapping(composeObject *types.Config) (kobject.Kompose
// Parse the volumes // Parse the volumes
// Again, in v3, we use the "long syntax" for volumes in terms of parsing // Again, in v3, we use the "long syntax" for volumes in terms of parsing
// https://docs.docker.com/compose/compose-file/#long-syntax-2 // https://docs.docker.com/compose/compose-file/#long-syntax-3
serviceConfig.VolList = loadV3Volumes(composeServiceConfig.Volumes) serviceConfig.VolList = loadV3Volumes(composeServiceConfig.Volumes)
// Label handler // Label handler