kompose does not indicate key nor line number when printing error

[alexanderkjeldaas]

This output:

 $ kompose convert -f ./docker-compose.yml
FATA configs Additional property configs is not allowed

Gives mostly no information:

1. No line number information
2. No yaml key
3. No jq style location
4. No excerpt from the input file.
5. It refers to "property config" where none of those words appear in the input.

[alexanderkjeldaas]

Ah, the configs is the key apparently. I suggest adding line numbers for this to understandable.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fentas]

Meaning that configs is not supported yet? Having the same problem.

edit: guess not ~ #994

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[bbros-dev]

/remove-lifecycle rotten
/remove-lifecycle stale
/reopen

[k8s-ci-robot]

@bbros-dev: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/remove-lifecycle rotten
/remove-lifecycle stale
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.