https://github.com/optimics/docker-terraform
Fruitful docker image to power up Bitbucket Pipelines deployments
https://github.com/optimics/docker-terraform
Last synced: 26 days ago
JSON representation
Fruitful docker image to power up Bitbucket Pipelines deployments
- Host: GitHub
- URL: https://github.com/optimics/docker-terraform
- Owner: optimics
- Created: 2022-03-09T18:57:34.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2023-07-03T08:55:42.000Z (almost 3 years ago)
- Last Synced: 2025-01-06T01:41:29.667Z (over 1 year ago)
- Language: Shell
- Size: 21.5 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Docker: optimics/terraform
[](https://github.com/optimics/docker-terraform/actions)
[](https://github.com/optimics/docker-terraform/tags)
[](https://hub.docker.com/r/optimics/terraform)
[](https://hub.docker.com/r/optimics/terraform)
A fruitful image that puts together several tools to make Continuous Deliveries and Continuous Deployments on Bitbucket Pipelines easy.
* [git](https://git-scm.com/)
* [Google Cloud SDK](https://cloud.google.com/sdk/)
* [Node.JS](https://nodejs.org/) with [npm](https://www.npmjs.com/)
* [descope-env](./descope-env.sh)
* [init-gcs](./init-gcs.sh)
* [Poetry](https://python-poetry.org/)
* [Terraform](https://www.terraform.io/cli/commands)
## `descope-env`
A tiny script that removes scope from your variables. Use this if you have mixed environment variables set in your system. There is no need to do additional variable mapping, which can save your pipeline definition size.
```shell
export STAGING_MYSQL_PASSWORD=password123
descope-env staging
echo $MYSQL_PASSWORD
# password123
```
First argument to this script is the actual environment. It can be omitted and passed as `PROJECT_ENVIRONMENT` env variable instead. If none is set, descope-env considers it the staging environment. If the variable `BITBUCKET_TAG` contains semver tag, it is considered the production environment.
### with package.json
Given `package.json` is present in the working directory, the `descope-env` will apply any key/value pairs from the `env` section into current environment.
## `init-gcs`
Also a tiny script that initializes Terraform Google Cloud Storage Backend and sets up a service account based on the credentials stored in `TF_VAR_GOOGLE_CREDENTIALS`. It takes no arguments. Make sure the `TF_VAR_BUCKET_TERRAFORM` contains the terraform state bucket.
## Usage
```
definitions:
steps:
- step: &deploy
name: Deploy Infrastructure
image: optimics/terraform:0.4
script:
- . descope-env
- init-gcs
- terraform validate
- terraform apply --input=false --auto-approve
branches:
master:
- step: *deploy
tags:
'v*':
- step: *deploy
```