-
Notifications
You must be signed in to change notification settings - Fork 59
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
Add GCP support for express cli #187
Conversation
…nto gangadhars-wip
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.
Thanks for the PR 🙌
Despite being a draft, I left some preliminary comments to help you solve some issues I see before getting to a finalised version, and also to start a conversation on some open points.
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.
Please resolve the (minor) comments.
Else, LGTM, thanks
Also, please solve prettier and linter issues, thanks |
There's a typo in the PR description
|
Updated |
Please also update region > eu-west-1 |
Code LGTM, hence approved. There might be some more changes required after testing. |
The setup fails in case of GCP with the following error:
The command
|
We need to update the documentation as well. There aren't any instructions on how we can install and configure gcloud ( |
|
Can you share your
Is this correct or is there any other way to setup gcloud on the local machine? For your reference this is my
|
Description
This pull request adds support for GCP in express-cli. Users can now provision the infra in either AWS or GCP using the
--init
option with the valuesaws
orgcp
.To identify which cloud the user has provisioned, we leverage the file remote-setup-config.yaml. When the user runs
--start
, we append the cloud details to remote-setup-config.yaml as shown below:For GCP
For AWS:
Changes
--init
option.remote-setup-config.yaml
to include cloud details--aws-key-add
to--ssh-key-add
and updated relative js files to handle both AWS and GCPBreaking changes
During our testing, we did not observe any breaking changes resulting from the current modifications. However, it appears that few functionalities breaking due to existing code. (note: these issues are not consistently reproducible.)
Checklist
Cross repository changes
None
Testing