BIGTOP-2712: Juju CI driven updates #189
Closed
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.
The original point of this branch was to refresh the hbase charm (readme was out-of-date, needed lint love). However, as soon as ran CI on this and recent changes from #187, it was like I opened a filthy can of yarn (or however that saying goes).
None of these are show-stoppers, but all of them are issues that could affect the UX when deploying/testing bigtop charms:
<charm>-test
for testing, and destroy it when done.As mentioned earlier, none of these issues affect charm functionality, but they do resolve test issues that might bite a user. This should be a trivial add and I am confident I can get good test runs before 1.2 goes RC.