error out when configurations do not match

[nabuskey]

fixes: #416

if a cluster was created with a configuration, then a different configuration is passed for the same cluster, error out.

./idpbuilder create

./idpbuilder create --use-path-routing
Oct 17 20:39:41 INFO Creating kind cluster logger=setup
Oct 17 20:39:41 INFO Runtime detected logger=setup provider=docker
Oct 17 20:39:41 INFO Cluster already exists logger=setup cluster=localdev
Oct 17 20:39:41 INFO Adding CRDs to the cluster logger=setup
Oct 17 20:39:41 INFO Setting up CoreDNS logger=setup
Oct 17 20:39:41 INFO Setting up TLS certificate logger=setup
Oct 17 20:39:41 ERROR Error while checking incompatible flags logger=setup err=provided command flags and existing configurations are incompatible. please recreate the cluster. existing: {Protocol:https Host:cnoe.localtest.me IngressHost:cnoe.localtest.me Port:8443 UsePathRouting:false SelfSignedCert:}, given: {Protocol:https Host:cnoe.localtest.me IngressHost:cnoe.localtest.me Port:8443 UsePathRouting:true SelfSignedCert:}
Error: :provided command flags and existing configurations are incompatible. please recreate the cluster. existing: {Protocol:https Host:cnoe.localtest.me IngressHost:cnoe.localtest.me Port:8443 UsePathRouting:false SelfSignedCert:}, given: {Protocol:https Host:cnoe.localtest.me IngressHost:cnoe.localtest.me Port:8443 UsePathRouting:true SelfSignedCert:}

[blakeromano]

overall looks good just some questions about types we are choosing

[blakeromano]

I mean maybe a nit but do we ever expect to have other kind of routing where we want to make this an enum string?

[nabuskey]

Hmm I honestly cannot think of other ways to route for now. Maybe this is something we can take a look at later along with the potential changes to the name of the flag. #417