Remove inbuilt dashboard since we are moving to use a separate charm #13370
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.
We are moving to deploy the juju dashboard using a charm instead of it being served by the controller.
This means that the workflow and CLI around locating and pulling a dashboard tarball from simplestreams and uploading it to the controller and extracting it and providing http endpoints on the controller API etc are all no longer needed.
Also tweak the controller-url config for the controller charm to include the port.
QA steps
juju bootstrap --no-default-model
(see that no dashboard messages are logged)
Bug reference
https://bugs.launchpad.net/juju/+bug/1945363