Improve jujudata to find controller name by endpoint #964
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This allows all kinds of connections to set the
controller_name
by default by looking up theendpoints
in thejujudata
.Fixes #771
QA Steps
Manual QA should follow the steps described in #771.
Find the details of a controller you bootstrapped (any controller would do):
Grab the details there and plug them into either a script or in the repl (repl is awkward to use with the certificate):
All CI tests need to pass.
Notes & Discussion
JUJU-4781