This repository has been archived by the owner on Sep 3, 2022. It is now read-only.
Set up script for Composer and support for getting gcsDagLocation from Composer environment #585
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| ZONE=us-central1 | ||
| PROJECT=$1 | ||
| EMAIL=$2 | ||
| ZONE=$3 | ||
| ENVIRONMENT=$4 | ||
|
|
||
|
|
||
| gcloud config set project $PROJECT | ||
| gcloud auth login --activate $EMAIL | ||
| sudo gcloud components repositories add https://storage.googleapis.com/composer-trusted-tester/components-2.json | ||
|
There was a problem hiding this comment. First thing is to install composer specific gcloud and it may vary slightly depending on the environment (e.g., VM, shell, local) before any gcloud * operations. |
||
|
|
||
| #gcloud components update -q | ||
| sudo apt-get update | ||
| sudo apt-get --only-upgrade install kubectl google-cloud-sdk google-cloud-sdk-datastore-emulator \ | ||
| google-cloud-sdk-pubsub-emulator google-cloud-sdk-app-engine-go google-cloud-sdk-app-engine-java \ | ||
| google-cloud-sdk-app-engine-python google-cloud-sdk-cbt google-cloud-sdk-bigtable-emulator \ | ||
| google-cloud-sdk-datalab | ||
|
There was a problem hiding this comment. We can put apt-get first, and then composer gcloud installation, and finally composer related configs and environment creation. |
||
|
|
||
| #gcloud components install -q alpha kubectl | ||
| sudo apt-get install google-cloud-sdk kubectl | ||
|
|
||
| gcloud config set composer/location $ZONE | ||
| gcloud alpha composer environments create $ENVIRONMENT | ||
| gcloud alpha composer environments describe $ENVIRONMENT | ||
|
|
||
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.
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.
--activate is the default
Is this setup.sh only ever run manually? (Asking because users shouldn't gcloud auth login on a VM.)
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, setup.sh is only ever run manually on a local machine at the moment. It's not for the VM scenario.
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.
(Removed --activate)