Open aliok opened 1 year ago
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen
. Mark the issue as
fresh by adding the comment /remove-lifecycle stale
.
cc @matzew
yes this would be super helpful
If we do this improvement, we can use these templates as-is in Backstage.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen
. Mark the issue as
fresh by adding the comment /remove-lifecycle stale
.
/reopen /remove-lifecycle stale
@aliok: Reopened this issue.
@matzew @lkingland What do you think?
@matzew @lkingland What do you think?
Yes, I would like to explore offering more customizable templates and integration with Backstage.
Let's discuss how this might work in practice either async via Slack or a meeting; at your convenience. I have a few thoughts.
When I create a NodeJS HTTP func using the template, I see it is always created with the same package name:
http-handler
: https://github.com/knative/func/blob/main/templates/node/http/package.json#L2It would be useful to make some[^1] of these hardcoded values placeholders.
Something like this:
which can generate something like:
Current hardcoded values can be the defaults.
While
name
is just very simple and doesn't provide much value, having ports, builders, baseImages, etc. can be very useful.Context:
[^1]: Definition of what to keep hardcoded and what to parametrize needs some work.