https://github.com/city-of-helsinki/review-services-action

Action to handle service's needed for review environment
https://github.com/city-of-helsinki/review-services-action

Last synced: 6 days ago
JSON representation

Action to handle service's needed for review environment

• Host: GitHub
• URL: https://github.com/city-of-helsinki/review-services-action
• Owner: City-of-Helsinki
• License: mit
• Created: 2021-05-04T12:53:46.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2023-11-16T03:48:52.000Z (about 1 year ago)
• Last Synced: 2024-11-18T23:15:53.627Z (2 months ago)
• Language: TypeScript
• Size: 1.27 MB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# review-services-action

Action to handle service's needed for review environment.

## Configuration

Following input variables are used in the action. Values without default value are mandatory.

| Name                    | Description                                                                                                | Default value |

| ----------------------- | ---------------------------------------------------------------------------------------------------------- | :-----------: |

| `kubeconfig`            | Kubeconfig as text to allow access to cluster and namespaces (RBAC) to create/get/delete jobs and secrets. |               |

| `namespace`             | Namespace of where application (and job) is deployed to                                                    |               |

| `action`                | What should be done. Possible options `create` and `remove`                                                |    create     |

| `default_database_name` | Name of the database that exists in postgres, as `psql` have to connect to DB before can create one        |   defaultdb   |

| `database`              | Name of the database to create                                                                             |               |

| `db_user`               | Admin user of database that can *create* and *drop* databases                                              |      ""       |

| `db_password`           | Password of admin user                                                                                     |               |

| `db_host`               | psql host                                                                                                  |               |

| `db_port`               | post that Postgres answers from                                                                            |               |

## Other options

### [kolga-deploy-service-action](https://github.com/andersinno/kolga-deploy-service-action)

Deploy-service-action deploys service in own container, once per namespace and service needed. It also creates persistent volume for the service (if applicable).

#### Cons

- Persistent volume is bound to zone, so if pod is evicted it has to be able to get to same zone or it's not started

- Amount of volumes and extra resource usage can get high if there's multiple PR open

- Different approach than with other environments

- No support for multiple DB in namespace (which might happen e.g. with monorepos)

#### Pros

- Doesn't require separate database accessible from cluster

- Removed along review environment