Due to #3578, and the fix (drop go-getter) in #3586, the set of URLs accepted by kustomize build is reduced
to only file system paths or values compatible with git clone (so, for example, mercurial and S3 no longer supported).
This backward incompatibility triggers a major version increment.
The same goes for elements of the resources field in kustomization.yaml (details in #3578).
Users that rely on special URLs in resource fields may use v3.10.0 or earlier.
We hope someone will write a plugin to restore this option, albeit with a new syntax.
Alternatively, we can refactor code to accept a new loader that would have to live outside kustomize/kustomize and outside kustomize/api (i.e. not on any path imported by kubectl or someone else).
1c3832f Increment major version from v3 to v4
cd0d416 Pin to api v0.8.1
8d75824 Pin to cmd/config v0.9.2
50bfa05 Pin to kyaml v0.10.10
b553997 Make more high level build methods public.
003b494 Delete --enable_kyaml flag.
9dc4004 Tidy go.sum after dropping go-getter.
a815774 Drop the go-getter dependence.
17ecec2 Kustomize file should be ignored when adding resources and components
e33addc Drop hashicorp multierror due to MPL
2d2fbe9 Unpin everything, back to development mode.