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.

Sign up for GitHub

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

Jump to bottom

Move flow-builder image out of Flow repo #21

Closed
iperdomo opened this issue Jan 6, 2020 · 0 comments
Closed

Move flow-builder image out of Flow repo #21

iperdomo opened this issue Jan 6, 2020 · 0 comments
Assignees
@iperdomo

Comments

@iperdomo
Copy link
Contributor

iperdomo commented Jan 6, 2020

The akvo/flow-builder image used for development and CI doesn't change so frequent.
We can cache the execution build and avoid repetitive work.
@iperdomo iperdomo self-assigned this Jan 6, 2020
iperdomo added a commit that referenced this issue Jan 6, 2020
@iperdomo
[#21] Move akvo/flow-builder from akvo/akvo-flow
7d8f839
iperdomo added a commit that referenced this issue Jan 6, 2020
@iperdomo
[#21] Pin versions of installed packages
593bee7
@iperdomo iperdomo mentioned this issue Jan 7, 2020
Closed
@iperdomo iperdomo closed this as completed Jan 7, 2020
iperdomo added a commit that referenced this issue Jan 15, 2020
@iperdomo
[#21] Refactor - Use published google/cloud-sdk as base
ab6da76 
Since we're using `node` for "bundling" the client application,
there is no need for BUNDLE_GEMFILE and other ruby related dependencies
iperdomo added a commit that referenced this issue Jan 15, 2020
@iperdomo
[#21] We need py-openssl and CLOUDSDK_PYTHON_SITEPACKAGES=1
012ea0b 
In order to activate a service account using the old (and deprecated)
.p12 files. We require this `py-openssl` and the environment
variable `CLOUDSDK_PYTHON_SITEPACKAGES=1`

More info: https://cloud.google.com/sdk/crypto
iperdomo added a commit that referenced this issue Apr 27, 2020
@iperdomo
[#21] Update flow-builder to latest gcloud SDK
da8c2ee
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iperdomo iperdomo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iperdomo