zarf init --registry flag gets cached

[supcom234]

WARNING Retrying (1/3): Get "https://10.254.2.170:31999/v2/": dial tcp 10.254.2.170:31999: connect: connection refused; Get "http://10.254.2.170:31999/v2/": dial tcp 10.254.2.170:31999: connect: connection refused ^C ERROR: execution cancelled due to an interrupt ubuntu@server1:~/zarf$ zarf init --components git-server --confirm --registry-url 127.0.0.1:31999 --registry-push-username zarf-push --registry-push-password password --registry-pull-username zarf-pull --registry-pull-password password

--registry-url gets cached as the error has 10.254.2.170 when I explicitly set it to 127.0.0.1
I tried
zarf tools clear-cache
and
zarf tools update-creds

The only thing that clears it was
zarf destroy --confirm
This was not intuitive as command line flags should override whatever was cached.

[lucasrod16]

@supcom234 if you intend on using the internal Zarf registry at 127.0.0.1:31999, you do not need to use any of the --registry-* flags with zarf init. The --registry-* flags allow you to use Zarf with an already existing registry and tells Zarf to not deploy a registry for you: https://docs.zarf.dev/ref/init-package/#using-external-registries

[supcom234]

@lucasrod16 I had to use an external docker registry because if I use the internal registry that gets deployed within Kubernetes you cant reboot, power down / power on the VM. The internal registry does not recover due to a cyclic dependency.