-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experimenting with giving developers the ability to choose their database with Humanitec #137
base: idp-plugins
Are you sure you want to change the base?
Conversation
In order to standup the executable delivery mechanism, we just hard-coded everything to be local development values and a fixed version of the executable name. However, the entire point is that everyone gets their own internal developer platform that is unique to them. We want to be able to customize that experience and also have it work in production environments. This adds the `executableName`, and `appURL` parameter to `createRouter` where you can pass in the specific name that you want your binary package to have. It will then compile it as that executable, and adjust the install script using a nunjucks template.
customize the executable name and URL
One of the really nice things about having your own developer platform is that we can configure the compiled binary to talk back directly to the server it was downloaded from. To accomplish this, we "statically" pass the executable name, the backend url, and the platform description as arguments to the compilation. That way we can use them not only to generate help and binary info for diagnostic purposes, but we will obviously need the url to connect to the backstage server.
Add basic help and info commands
Add info command
* add scaffold cli action * rename scaffold to create * allow yaml argument to create from file or stdin
Adding clone command
Add streaming logs command and endpoint.
Deployment environment output in `idp` cli
|
📣 NOTIFICATION Generated by @thefrontside/actions |
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.I would expect the infrastructure profile take
PostgreSQL 15
,PostgreSQL 14.5
orPostgreSQL 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
🤷