chore(bitgo): bitgo proposal to have 2 envs #851
Merged
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
zone-live
changed the title
zone-live
changed the title
albertolive
approved these changes
Oct 22, 2024
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.
Description
Slack reference thread: https://consensys.slack.com/archives/C029JGUQKH8/p1726763493221839?thread_ts=1721940583.862139&cid=C029JGUQKH8
Bitgo asked us to support their test env in production as well, so we added a new bitgo environment entry to prod config API as
bitgo-test.And did the necessary changes, change the new env type to be "Bitgo", in mmi configuration and in bitgo keyring if the name is not "bitgo" it means the env being requested is the test env "bitgo-test".