backstage
backstage copied to clipboard
Declarative CLI Templates
Hey, I just made a Pull Request!
Remaining TODOs
- [ ] Read templates from a URL
- [ ] Compose names for modules with id prompt
- [ ] Prompt validators? (see comment)
- [ ] Automatically install packages to backend/app? (see comment)
:heavy_check_mark: Checklist
Missing Changesets
The following package(s) are changed by this PR but do not have a changeset:
- @backstage/cli
See CONTRIBUTING.md for more information about how to add changesets.
Changed Packages
| Package Name | Package Path | Changeset Bump | Current Version |
|---|---|---|---|
| @backstage/cli | packages/cli | none | v0.28.0-next.0 |
- I didn't include any CLI flag options. I assume things like
private,npm-registry, andlicensecan now be written right into the template. Or if these templates are used by companies that have teams that need to configure separate registries, they could always make that a required prompt. - Do we still want to accommodate for Lerna users for setting the base version?
- I was thinking of having newly created packages be automatically installed to the backend or the app depending on the role specified in
package.json. Thoughts? - Should I look for a way for users to be able to provide validators for their prompts? I have the default validator used for plugin and module id prompt as a placeholder, but clearly that validator won't apply to every use-case.
Regarding lerna, yeah we can remove that. Thinking we just make it a global option instead
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!
Are there any chances this can be re-opened? Sounds like a cool feature!
@minkimcello we can't re-open this PR, can you create a new one? :pray:
@minkimcello we can't re-open this PR, can you create a new one? 🙏
@benjdlambert Ah okay. Sure 👍
Hi @minkimcello, do you happen to have a rough ETA on the new PR to keep moving this forward?
@awanlin @benjdlambert @Rugvip #27934 i just rebased and opened up a new PR. i'll put some more time into it this weekend.