Resolve issue causing missing endpoints in cluster config

[Steven Gagniere (sgagniere)]

Checklist

1. [CRUCIAL] Is the change for CP or CCloud functionalities that are already live in prod?
   • yes: ok

What

Calling FindKafkaCluster in dynamic_context.go before the cluster has finished provisioning causes the cluster info to be saved in config.json with bootstrap_servers equal to "" and no api_endpoint or rest_endpoint. As the config is only updated after at least one week since the timestamp saved in config.json, this prevents use of the cluster unless the timestamp is manually changed to trick the CLI into thinking it should be updated.

Found by calling kafka cluster describe on a provisioning cluster; this command now uses kafka REST for one of the description fields. Other commands using kafka REST also create this issue, e.g. kafka topic commands.

This PR makes a single change: if the config is not nil and Bootstrap is the empty string, then refresh the config.

References

n/a

Test & Review

Tested by calling kafka cluster describe on a provisioning cluster, and then again after it finished provisioning to check that it now prints the description as expected.

Open questions / Follow ups

Follow ups:

• Modify kafka cluster describe to not check for topics while the status is PROVISIONING and instead print an empty value. This command still errors out at the moment.
• Remove the backup code and/or improve the error messaging when commands using kafka REST are called during provisioning. Currently, the CLI prints an arcane backend error about empty schemas.

[David Hyde (DABH)]

+1 once CI passes!

[Brian Strauch (brianstrauch)]

Want to use a more realistic value here?

[Steven Gagniere (sgagniere)]

How about this new version?