6af3da8d7b
Change 725820 [1] configured airshipctl to fail an airship config file isn't present. The present change makes an exception to that behavior for the document plugin subcommand, and moves the plugin loading from the parent document command into the pull subcommand. There are multiple reasons we don't want config enforcement in place for plugins: - If a non-standard config file location is configured via an environment variable, the plugin won't know about it (since it's invoked separately by kustomize), and it would look for a potentially non-existant default config file, and fail. - If a user is using the kustomize cli by hand along with airshipctl plugins (as opposed to driving the process via airshipctl itself), then they do not need the config anyway -- the plugin subcommand doesn't actually use it. Forcing the user to create a config file seems awkward here. [1]: https://review.opendev.org/#/c/725820/16 Change-Id: Ic1b652efb14439ed2757eb9fb0a86feb8b3ef21c |
||
|---|---|---|
| .. | ||
| testdata | ||
| document_test.go | ||
| document.go | ||
| plugin_test.go | ||
| plugin.go | ||
| pull_test.go | ||
| pull.go | ||