POC of Platform API Plugin and an IDP CLI #103
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
|
|
📣 NOTIFICATION Generated by @thefrontside/actions |
taras
commented
Oct 5, 2022
packages/backend/src/index.ts
Outdated
| @@ -92,6 +93,7 @@ async function main() { | |||
| const searchEnv = useHotMemoize(module, () => createEnv('search')); | |||
| const appEnv = useHotMemoize(module, () => createEnv('app')); | |||
| const humanitecEnv = useHotMemoize(module, () => createEnv('humanitec')); | |||
| const ldpEnv = useHotMemoize(module, () => createEnv('ldp')); | |||
There was a problem hiding this comment.
FYI: it's internal developer platform - IDP, not LDP.
|
The skeleton starts to walk around!
|
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.
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 scaffold cli action * rename scaffold to create * allow yaml argument to create from file or stdin
taras
changed the title
2 tasks
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
We're getting started putting together a demo of #99 and we need to start adding plugins that'll have all of the necessary pieces in them.
Approach
Created
@frontside/backstage-plugin-platformand@frontside/backstage-plugin-platform-backend