https://github.com/hden/run-env

Manage multiple deployment profiles for Google Cloud Run
https://github.com/hden/run-env

Last synced: 28 days ago
JSON representation

Manage multiple deployment profiles for Google Cloud Run

• Host: GitHub
• URL: https://github.com/hden/run-env
• Owner: hden
• License: mit
• Created: 2019-10-15T13:12:14.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2024-10-29T08:26:11.000Z (2 months ago)
• Last Synced: 2024-10-29T09:47:35.621Z (2 months ago)
• Language: Clojure
• Homepage:
• Size: 2.4 MB
• Stars: 2
• Watchers: 6
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# run-env [![CircleCI](https://circleci.com/gh/hden/run-env/tree/master.svg?style=svg)](https://circleci.com/gh/hden/run-env/tree/master)

Manage multiple deployment profiles for Google Cloud Run.

## Usage

Cloud Run's cost model fits very well with multiple staging environments.

For example, you might want to deploy multiple services with slightly different

environmental variables (e.g. different Cloud SQL connection). Although Google

offers a friendly UI, it's not very helpful when you need to manage multiple

profiles within a CI/CD pipeline.

Here is an example of running two environments.

```dev.json

{

  "name": "hello",

  "image": "gcr.io/cloudrun/hello",

  "platform": "managed",

  "concurrency": 10,

  "max-instances": 1,

  "memory": "512Mi",

  "region": "asia-northeast1",

  "env": {

    "MYSQL_USER": "local",

    "MYSQL_PASSWORD": "berglas://my-bucket/mysql-password-dev"

  },

  "cloudsql-instances": [

    "staging"

  ]

}

```

When you want to override some, but not all parameters, run-env can automatically

read from other profiles using the **include** key.

```prod.json

{

  "include": ["dev.json"],

  "max-instances": 10,

  "allow-unauthenticated": true,

  "env": {

    "MYSQL_USER": "production",

    "MYSQL_PASSWORD": "berglas://my-bucket/mysql-password-prod"

  },

  "cloudsql-instances": [

    "production"

  ]

}

```

Several feature that might be extra helpful:

* You can **include** multiple files.

* You can nest multiple files.

* When used with tools like [berglas](https://github.com/GoogleCloudPlatform/berglas), the sensitive information can be safely encrypted and stored, outside of your git repository.

* Text fields supports shell-like interpolation so you can dynamically configure service name (e.g. `prefix-$CIRCLE_BRANCH`).

## License

MIT