-
Notifications
You must be signed in to change notification settings - Fork 17
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: mainnet test deploy #712
Conversation
…maus-near/deployment-docs
…ear/mpc-recovery into kmaus-near/mainnet-test-deploy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this not the latest develop branch?
}, | ||
{ | ||
name = "MPC_RECOVERY_CONTRACT_ID" | ||
value = "v2.multichain-mpc.testnet" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will need to change too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are still waiting on naming this contract no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is there no infra/partner-multichain/variables.tf like all the other directories nvm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think directory infra/scripts/generate_cipher_and_sign_keys
need to be deleted.
multichain-account-sk-mainnet-0=foo | ||
multichain-cipher-sk-mainnet-0=bar | ||
multichain-sign-sk-mainnet-0=baz | ||
multichain-sk-share-mainnet-0=qux |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's do multichain-sk-share-mainnet-0=1
here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just have this as an example, ideally this file will get deleted after they are uploaded to SM and we have everything working.
@@ -0,0 +1,4 @@ | |||
multichain-account-sk-mainnet-0=foo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also will this have any danger of including \n or space? in the secret?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I accounted for that in the script itself, so as long as they follow this format ("secret-name"="sec-val" ) it will work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah nice!
Closes #678 |
Terraform Feature Environment Destroy (dev-712)Terraform Initialization ⚙️
|
This PR also contains the proposed partner mainnet TF code, please spend some time to review and ask questions on anything.