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

Deploy to separate GCP project #122

Closed
MichaelAkvo opened this issue Apr 12, 2022 · 0 comments · May be fixed by #134
Closed

Deploy to separate GCP project #122

MichaelAkvo opened this issue Apr 12, 2022 · 0 comments · May be fixed by #134
Assignees
@MichaelAkvo

Comments

@MichaelAkvo
Copy link

The customer requirements are very stringent regarding access to data. In order to fulfill those requirements, the project is being deployed to a separate GCP project. Previously done manually, now this has to be done by the CI.
@MichaelAkvo MichaelAkvo self-assigned this Apr 12, 2022
dedenbangkit added a commit that referenced this issue Apr 12, 2022
@dedenbangkit
[#122] Copy source from local to kubernetes script
3d2636b
dedenbangkit added a commit that referenced this issue Apr 12, 2022
@dedenbangkit
[#122] Migrate database from A to B
227b602
MichaelAkvo added a commit that referenced this issue Apr 13, 2022
@MichaelAkvo
refactor: Rename deployment.yml.template
1f4742f 
The file ending helps with syntax highlighting

#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 13, 2022
@MichaelAkvo
ci: Use IMAGE_PREFIX for docker images
11632ef 
This will allow specifying where to push the images right from semaphore

#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 13, 2022
@MichaelAkvo
ci: support deploying to a custom GCP project
5921147 
The GCP project was hardcoded, but now it's possible to specify a different one
 using environment variables.

#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 13, 2022
@MichaelAkvo
ci: Move checkout command to global prologue
ec1e9e5 
All tasks will need the repo

#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 13, 2022
@MichaelAkvo
ci: Add FORCE_BUILD variable
12e9f12 
Sometimes we just want to check if the build is working or to force a new one

#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 13, 2022
@MichaelAkvo
ci: Use new secrets
8e7145b 
New env vars were introduced for deploying and building.
These are now in SemaphoreCI

#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 13, 2022
@MichaelAkvo
ci: Test deploy.sh
f929b58 
#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 14, 2022
@MichaelAkvo
ci: Test deploy.sh
ca80a5e 
#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 14, 2022
@MichaelAkvo
ci: Support deploying to test and production
9a522ac 
Env vars with prefixes have to be present and they are then stripped of their prefix
 depending on which env to deploy to.

IMAGE_PREFIX is now only used in the deploy script as it's the only one that realistically needs it.

#122: Deploy to separate GCP project
@MichaelAkvo MichaelAkvo mentioned this issue Apr 14, 2022
Draft
MichaelAkvo added a commit that referenced this issue Apr 14, 2022
@MichaelAkvo
test deploy
97aaead 
#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 14, 2022
@MichaelAkvo
ci: Use semaphore to promote to production
805c8d4 
#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 14, 2022
@MichaelAkvo
ci: Use semaphore to promote to production
23d2ed1 
#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 14, 2022
@MichaelAkvo
ci: Support deploying to test and production
67849ab 
Env vars with prefixes have to be present and they are then stripped of their prefix
 depending on which env to deploy to.

IMAGE_PREFIX is now only used in the deploy script as it's the only one that realistically needs it.

#122: Deploy to separate GCP project
MichaelAkvo added a commit that referenced this issue Apr 14, 2022
@MichaelAkvo
ci: Use semaphore to promote to production
1edd439 
#122: Deploy to separate GCP project
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MichaelAkvo MichaelAkvo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support deployment to separate gcp project akvo/isco
2 participants
@wayangalihpratama @MichaelAkvo