Skip to content
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

skaffold init should not fail on existing skaffold.yaml if it's pointing to another skaffold.yaml #3554

Closed
balopat opened this issue Jan 22, 2020 · 0 comments · Fixed by #3575
Labels
area/init kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@balopat
Copy link
Contributor

balopat commented Jan 22, 2020

When an existing skaffold.yaml might be overriden by the skaffold init execution we should warn the user. This is why we throw an error: pre-existing skaffold.yaml found (you may continue with --force)

This should be avoided when the target configuration is a different file from the existing skaffold.yaml file, e.g.:

  • the file is in a different directory
  • -f different_skaffold.yaml is passed in

Also, if --analyze passed in, we can ignore this error, as skaffold is not writing a skaffold.yaml file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/init kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
1 participant