Remove trusty support from the layer #36
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
What specifically changed to make the latest etcd charm incompatible with the trusty charm? We should also update the readme with this information (directory where the files are stored, or whatever), and how users should turn up a new etcd cluster if they were using the old incompatible one. |
|
Good insight, i'll get that added an commit an update. |
|
superseded by #37 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Trusty doesn't have an archive option for installing etcd. The big
line items this resolves is crossing the barrier from tls by default.
Trusty series published versions of this charm have all been targeting
development channels. I feel this is a good time to break that backwords
compat and move forward with tls by default in xenial.