Conversation
…ents and add tested usage examples
…lient enroll Ansible Role
e72b744 to
3d36648
Compare
Contributor
Author
|
cc: @pacospace , @ecusrc |
Contributor
Author
|
@tervo I am closing this PR based on your remarks from today, as it is unclear on our side what is considered a "contribution" to and "ownership" of a EWC-supported Item in the context of the Community Hub. |
This file contains hidden or 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
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.
Hello again @xavierabellan
This is the follow up PR we promised to publish default stack flavours.
What's new?
Ansible Playbooks for configuring :
provisioningandteardownphases.Additionally:
7. new references to the required Ansible Roles (pending for release and currently under EUMETSAT quality assurance review)
What stays the same?
Self-provisioning Ansible Playbooks (i.e. Terraform under the hood) are kept out of the PR, as you voiced concerns that sort of items go beyond the scope of this repository.
Is this PR worthy of a new release branch?
Yes, a
feat:prefix on the squash-merge operation is advised so that we go into2.1.0