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

Feat: Add 12 Dev nodes/cleanup workflow files #872

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

kmaus-near
Copy link
Collaborator

A few things in this pull request, but should close #855 at least for Dev. Not sure if we will be running additional nodes ourselves or onboarding more partners, so we can leave that open if need be.

I also cleaned up and changed names of some of the Workflow files which would close #868. There is a roadmap for GitHub to release the ability to organize Workflows into folders, but it does not seem to be on their priority list for this year, so I think this is the best I can do as far as cleanup. I also set the Dev node deployment to be triggered manually, and it will restart the nodes each time, even if there are no changes. Let me know if there are any issues with what I've got.

@kmaus-near kmaus-near requested review from volovyks and ppca October 4, 2024 18:08
@kmaus-near kmaus-near self-assigned this Oct 4, 2024
Copy link
Collaborator

@volovyks volovyks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
@ppca please, take a look

@@ -156,6 +156,7 @@ resource "google_compute_instance_template" "tpl" {

lifecycle {
create_before_destroy = "true"
ignore_changes = [ disk[0].source_image, labels ]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this line mean?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this likely ignores whether image changes or not, whenever you push, the nodes will be updated.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, this was to stop any unnecessary redeployments when adding nodes.

@@ -1,42 +0,0 @@
name: Multichain Contract
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we deploy the contract now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By using deploy-multichain-dev-contract.yml, I don't think this workflow file is in use.

@@ -156,6 +156,7 @@ resource "google_compute_instance_template" "tpl" {

lifecycle {
create_before_destroy = "true"
ignore_changes = [ disk[0].source_image, labels ]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this likely ignores whether image changes or not, whenever you push, the nodes will be updated.

@kmaus-near kmaus-near merged commit 11dd7e0 into develop Oct 7, 2024
@kmaus-near kmaus-near deleted the kmaus-near/add-dev-nodes branch October 7, 2024 19:42
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.

Organize and improve GitHub acitons Scale the system to 10+ nodes
3 participants