Integration - Restructure GCZ Repo to satisfy OSDU Devops Standards
Summary
OSDU Core Services must follow a general standard for Devops and CI/CD related materials. The GCZ does not yet meet these standards, so CSPs are left to figure out how to navigate and understand our deployment guide without the assistance that this standardized structure can provide.
The intention is not immediately for the GCZ team to know exactly how the GCZ should be deployed on each and every cloud environment, but we need to meet a minimum level of structure and content standards to assist CSPs in closing the knowledge gap and improve integration with OSDU.
Acceptance Criteria
At a minimum, the GCZ repo requires:
- a devops folder in the root - Completed in #224 (closed)
- which contains one folder per CSP (aws, azure, gcp, ibm, etc.)
- each containing
deploy
andpipeline
folders- each containing
.yaml
files and README.md to document and provide deployment pipelines and support templates
- each containing
- each containing a README.md
- each containing
- which contains one folder per CSP (aws, azure, gcp, ibm, etc.)
Remaining work to be completed:
- The root-level
.gitlab-ci.yml
file must include the relevant.yaml
files (bootstrap, overrides, etc.) referenced in the devops folder, along with any essential Helm Chart info (as applicable) and environment variables organized per-csp (AWS_[ENV_VAR], IBM_[ENV_VAR], etc.) - A clear set of steps for deploying the GCZ's web services into a docker container
For implementation info on this request, please contact:
- David Diederich (@divido)
- Oleksandr Kosse (@Oleksandr_Kosse)
- Chad Leong (@chad)
- Debasis Chatterjee (@debasisc)
Resources
Edited by Joel Romero