Experimenting with giving developers the ability to choose their database with Humanitec #137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
taras
changed the title
taras
changed the title
taras
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.yamlfile 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.5orPostgreSQL 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
馃し