Improve configurability of deployment template #49
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
|
Hello, Is this repository actually open for contributions? |
gillesgagniard
changed the title
|
Added two other configurability improvements:
|
birdman100
approved these changes
Nov 17, 2020
birdman100
approved these changes
Nov 17, 2020
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.
Currently, the Couchbase DM template assumes there is a VPC named "default", that it is set in automatic subnet mode, and can only deploy Couchbase clusters there.
This pull request adds the ability to deploy to other networks (keeping "default" as the default obviously), and also to pass subnetwork information for networks which are in custom subnet mode.