jx icon indicating copy to clipboard operation
jx copied to clipboard

Custom place holders in quickstarts

Open msvticket opened this issue 6 years ago • 15 comments

Summary

Apart from the default place holders (REPLACE_ME_APP_NAME, REPLACE_ME_GIT_PROVIDER, REPLACE_ME_ORG and REPLACE_ME_DOCKER_REGISTRY_ORG) it would be practical to to be able to introduce custom place holders with specified prompt and default.

An example use case would be for a quickstart to ask user for groupId to put on pom.xml.

msvticket avatar Oct 01 '18 17:10 msvticket

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot avatar Jun 03 '19 22:06 jenkins-x-bot

/remove-lifecycle stale

msvticket avatar Jun 04 '19 09:06 msvticket

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot avatar Mar 13 '20 01:03 jenkins-x-bot

/remove-lifecycle stale

msvticket avatar Mar 13 '20 09:03 msvticket

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot avatar Jun 11 '20 10:06 jenkins-x-bot

/remove-lifecycle stale

msvticket avatar Jun 11 '20 11:06 msvticket

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot avatar Sep 09 '20 12:09 jenkins-x-bot

/remove-lifecycle stale

a-y-khan avatar Sep 17 '20 20:09 a-y-khan

I am an observer and asking this question out curiosity, not at all trying to be demanding. I am curious if it has ever been considered to just support some fairly standard templating language directly, rather than the rather custom and limited current state of things. Has this ever come up or been considered? If so, is there any sort of remnant or documentation about the conversation and decision that was made?

scizo avatar Sep 18 '20 00:09 scizo

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot avatar Dec 17 '20 01:12 jenkins-x-bot

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

jenkins-x-bot avatar Jan 16 '21 01:01 jenkins-x-bot

/remove-lifecycle rotten

msvticket avatar Jan 19 '21 10:01 msvticket

Hey, Do you have an idea if this is still something you're interested in?

Would this be an organisation wide replacement?

I'm assuming you would then have setup your own custom quickstarts/buildpacks.

tomhobson avatar Mar 12 '22 14:03 tomhobson

We do have custom quickstarts for our organization (mainly to get correct setup for monitoring and logging).

The point of this issue and also #1849 is to make it possible to create more flexible quickstarts.

My vision is that a quickstart could be configured to give further choices when you create a project using it. To solve these issues I created a long time ago wouldn't suffice to reach that vision though. The functionality should be useful both in the quickstarts in https://github.com/jenkins-x-quickstarts and one created for a specific organisation.

A couple of use cases of this functionality could be:

Choose integration with logging framework:

  • [ ] Filebeat
  • [ ] Fluentd

Do you want tot connect to a database? Yes

How?

  • [ ] Using credentials from secret
  • [ ] Getting credentials from vault

A part of this functionality exists for Jenkins-X 2 App: https://jenkins-x.io/docs/resources/guides/extending-jx/apps/

Similar functionality for the packs would be useful. A typical case to solve would be to unify the multiple build packs for maven that just differ in java version.

msvticket avatar Mar 23 '22 12:03 msvticket

Looking at GSOC there is the Quickstart Improvements area. Either that could be expanded or a separate idea could be added about improving the quickstart and pack functionality itself.

msvticket avatar Mar 23 '22 12:03 msvticket