Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When resetting and upgrading a VM testnet, new tx-nodes are included in the new instance group #771

Merged
merged 8 commits into from
Oct 3, 2019

Conversation

tkporter
Copy link
Contributor

Description

This ensures that when running celotooljs deploy upgrade vm-testnet --reset, the tx-node instance group includes the new tx-nodes. Because of some restraints imposed by Terraform, this is done by creating the tx-nodes and instance group before destroying it (this is the suggested behavior). In order to avoid name conflicts (which made GCP force the deployment to fail), random suffixes were added to the names of the resources.

Tested

Ran celotooljs deploy upgrade vm-testnet --reset and saw that the new tx-nodes were included in the new instance group

Other changes

n/a

Related issues

Backwards compatibility

Yes

@codecov
Copy link

codecov bot commented Aug 28, 2019

Codecov Report

Merging #771 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #771   +/-   ##
=======================================
  Coverage   66.16%   66.16%           
=======================================
  Files         261      261           
  Lines        7599     7599           
  Branches      440      440           
=======================================
  Hits         5028     5028           
  Misses       2476     2476           
  Partials       95       95
Flag Coverage Δ
#mobile 66.16% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f6eafb8...c80f944. Read the comment docs.

@ashishb ashishb closed this Sep 24, 2019
@ashishb ashishb deleted the trevor/vm-testnet-instance-group branch September 24, 2019 01:30
@ashishb ashishb restored the trevor/vm-testnet-instance-group branch September 24, 2019 02:11
@ashishb ashishb reopened this Sep 24, 2019
@timmoreton timmoreton assigned tkporter and unassigned timmoreton and nambrot Oct 3, 2019
@tkporter tkporter merged commit 7832f88 into master Oct 3, 2019
@tkporter tkporter deleted the trevor/vm-testnet-instance-group branch October 3, 2019 23:27
aaronmgdr added a commit that referenced this pull request Oct 4, 2019
* master:
  [Protocol] Fix network id for alfajores in truffle configs (#1211)
  When resetting and upgrading a VM testnet, new tx-nodes are included in the new instance group (#771)
  Upload static VM testnet nodes, add stackdriver logging (#750)
  Revert "Make packages depend on git vesrion (not npm)" (#1201)
  Make packages depend on git vesrion (not npm) (#1192)
  [contractkit] Document methods (#1195)
  [ck] consistent send tx object in kit (#1191)
  Move docker images to use node v10 (#1183)
  [ContractKit]Fill more fields before web3 signing (#1133)
  [codecov]Fix codecov errors (#1147)
  [Wallet] Add support for address pasting in send input field (#1180)
  Fix verification pool validation (#1176)
  Improve QR Code scan ability (#1036)
  Add CLI commands around identity metadata (#1167)
  [wallet]Run geth in an infura-like mode (#1108)

# Conflicts:
#	yarn.lock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When upgrading and resetting a VM testnet, the tx node instance group should include the new tx nodes
4 participants