Neither vip cleanup nor vip uninstall accepts --insecure or --ca-bundle, and neither reads [tls] settings for its own HTTP calls, so against a deployment using a self-signed or internal-CA certificate they fail with no way to proceed. vip verify supports both.
Surfaced while fixing #537: scheme resolution now correctly refuses to downgrade to plaintext when a TLS listener is present but untrusted, and prints guidance naming [tls] insecure / [tls] ca_bundle. For cleanup and uninstall that guidance is only half-actionable -- the config keys exist, but these commands have no flag equivalents, and a user passing --connect-url with no vip.toml has nowhere to set them.
Neither
vip cleanupnorvip uninstallaccepts--insecureor--ca-bundle, and neither reads[tls]settings for its own HTTP calls, so against a deployment using a self-signed or internal-CA certificate they fail with no way to proceed.vip verifysupports both.Surfaced while fixing #537: scheme resolution now correctly refuses to downgrade to plaintext when a TLS listener is present but untrusted, and prints guidance naming
[tls] insecure/[tls] ca_bundle. Forcleanupanduninstallthat guidance is only half-actionable -- the config keys exist, but these commands have no flag equivalents, and a user passing--connect-urlwith novip.tomlhas nowhere to set them.