Merge deploy-terraform
into dev-dhi-next
#418
Merged
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.
This adds support for the CI/CD workflow to the main
dev-dhi-next
branch in preparation for future iterations of thedeploy-terraform
branch. Deploying droplets using terraform/ansible should generally either use the currentdeploy-terraform
branch (which is guaranteed to be runnable via CI/CD) or a tagged commit (e.g. if deploying a specific commit point for a pilot study).The updates are basically what is defined in #404.
Specifcally:
nc-multiplex
andnetcreate-itest
)netcreate-config.js
file so thatnpm run package
can be run during provisioning on a fresh droplet install.