Print warning for unsupported fields in docker-compose format

[janetkuo]

Follow up #3

We're now printing warnings of unsupported fields in their names defined in libcompose, but not their names in docker-compose file format.

For example, this

$ cat nginx.yml
nginx:
  image: nginx
  dockerfile: foobar
  build: ./foobar
  cap_add:
    - ALL
  container_name: foobar

$ kompose convert -f nginx.yml
WARNING: Unsupported key Build - ignoring
WARNING: Unsupported key CapAdd - ignoring
WARNING: Unsupported key ContainerName - ignoring
WARNING: Unsupported key Dockerfile - ignoring

should give me the following warnings instead:

$ kompose convert -f nginx.yml
WARNING: Unsupported key build - ignoring
WARNING: Unsupported key cap_add - ignoring
WARNING: Unsupported key container_name - ignoring
WARNING: Unsupported key dockerfile - ignoring

[surajssd]

@janetkuo and @ngtuna why can we use logrus.Warningf instead of fmt.Println at https://github.com/skippbox/kompose/blob/master/cli/app/app.go#L1076 ?

[surajssd]

Also when doing --stdout the warnings should be either printed in a way so that user can still pipe the output to a kubectl. I am not sure if I should create a new issue for this?

[surajssd]

Using following docker-compose file

$ cat docker-compose.yml 
version: "2"

services:
  mariadb:
    image: centos/mariadb
    container_name: mariadb
    ports:
      - "3306"
    environment:
      MYSQL_ROOT_PASSWORD: etherpad
      MYSQL_DATABASE: etherpad
      MYSQL_PASSWORD: etherpad
      MYSQL_USER: etherpad

When directly piped fails

$ kompose convert  --stdout | kubectl --namespace=kompose create -f -
yaml: line 2: could not find expected ':'

Because the output starts with

$ kompose convert  --stdout
WARNING: Unsupported key Networks - ignoring
{
  "kind": "Service",
  "apiVersion": "v1",
[SNIP]

[ngtuna]

Good catch @janetkuo and @surajssd . Thanks. I will update shortly

[janetkuo]

Closing as this is now fixed by 55ae6e7

[janetkuo]

Right now there are unsupported keys / fields not covered by warnings, such as volume configs.

[surajssd]

@ngtuna yes its good that we have we now don't print the output to stdout so I can pipe output right now! 👍
And this can be closed it seems.

[ngtuna]

@janetkuo Agree. We haven't covered both volume configs and network configs.

[ngtuna]

Closed by 14cf356