You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not clear from the docs what directory kots pull will write to. https://kots.io/kots-cli/pull/ says that it defaults to /path/, which can't be right (surely it's not writing to the root of your file system).
kots pull --help says it writes to your home directory:
--rootdir string root directory that will be used to write the yaml to (default "/Users/gabe")
In practice, this appears to be what it does (create a directory under $HOME). But it would be better if it instead wrote to the current working directory. The current behavior is unexpected (much more common for tools to write to current directory rather than home directory), and somewhat dangerous (it will overwrite any files that happen to live at ~/$REPLICATED_APP/{base,overlays,skippedFiles,upstream}).
To its credit, kots pull does tell you exactly where it wrote its files after the fact ("Kubernetes application files created in ..."). So that helps somewhat.
The text was updated successfully, but these errors were encountered:
It's not clear from the docs what directory
kots pull
will write to. https://kots.io/kots-cli/pull/ says that it defaults to/path/
, which can't be right (surely it's not writing to the root of your file system).kots pull --help
says it writes to your home directory:In practice, this appears to be what it does (create a directory under
$HOME
). But it would be better if it instead wrote to the current working directory. The current behavior is unexpected (much more common for tools to write to current directory rather than home directory), and somewhat dangerous (it will overwrite any files that happen to live at~/$REPLICATED_APP/{base,overlays,skippedFiles,upstream}
).To its credit,
kots pull
does tell you exactly where it wrote its files after the fact ("Kubernetes application files created in ..."). So that helps somewhat.The text was updated successfully, but these errors were encountered: