Experimenting with giving developers the ability to choose their database with Humanitec

[taras]

Motivation

I want to show how developers can choose a database when creating a new service.

Approach

I added a configuration to the template that shows a dropdown with different PostgreSQL options. That value will be passed to the template. I would like to pass this information to the infrastructure profile. The infrasture profile should choose how to provide the database for the workload.

Here is the humanitec-app.yaml file that is used to generate JSON payload that's sent to the Humanitec API.

        profile: humanitec/default-module
          database: ${{ values.database }}

I would expect the infrastructure profile take PostgreSQL 15, PostgreSQL 14.5 or PostgreSQL 13. When deployed in development environment, it should run the PostgreSQL database as a workload in a container. When deployed in production, the database should be provisioned on the infrastructure.

Alternate Designs

🤷

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: ba9160a2f38871390e373802f71f6419b67e1628

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[frontsidejack]

📣 NOTIFICATION You are receiving this message because we did not publish any packages.

Generated by @thefrontside/actions