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

Fix opening data, align dev setup with production #43

Merged
merged 4 commits into from
Mar 30, 2021

Conversation

machow
Copy link
Contributor

@machow machow commented Mar 29, 2021

Address #42, #37

  • Dev environment
    • changes location of dags, plugins, and data to match composer
    • moved config mount to user's home directory
    • on dev use google_default authentication, and set GOOGLE_CLOUD_PROJECT env var
    • add COMPOSER_ENVIRONMENT="development" flag
  • Added calitpy.py module in plugins, to provide high-level functions (e.g. save_to_gcfs, which uses the test bucket on development). This can made a package down the line.
  • Updated README with instructions for generating the necessary gcloud config

@hunterowens
Copy link
Member

waiting on #42

@machow machow changed the title WIP: Fix opening data, align dev setup with production Fix opening data, align dev setup with production Mar 29, 2021
@machow machow requested a review from hunterowens March 29, 2021 19:26
@hunterowens hunterowens merged commit 6769240 into main Mar 30, 2021
@hunterowens hunterowens deleted the fix-opening-data branch March 30, 2021 20:14
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.

2 participants