tidy up the template questions

[gilesknap]

simplify the questions and add more help.

Points to note.
Target namespace, Apps namespace and Argo CD project are all the same string at DLS so I condensed down into a single question. If any external users want to set up ArgoCD we can recommend they use the same approach or generalize this template as necessary.

tested against i04 and p47.

Fixes #9

example interaction:

This template will create a new repository which describes the set of IOCs and services that Argo CD will track on a Kubernetes cluster.

🎤 A name for the group of IOC and service instances that this
   repository will track.

   At DLS this should be the short beamline name or the technical area
   for accelerator repos.
   i04
🎤 A One line description of the module
   i04 IOC Instances and Services Deployment Repository for Argo CD
🎤 Argocd server DNS Name.

   At DLS this is always "argocd.diamond.ac.uk"
   argocd.diamond.ac.uk
🎤 Cluster in which Argo CD Apps are deployed.

   At DLS this is always "argus"
   argus
🎤 The Kubernetes cluster where the IOCs and services will run.

   At DLS this should be "{beamline shortname}", "acastus" for the
   accelerator or "pollux" for test beamlines.
   i04
🎤 Kubernetes namespace in which the IOCs and services will run.

   At DLS this should be "{beamline shortname}-beamline" or "accelerator".
   i04-beamline
🎤 Git platform hosting this repository.
   gitlab.diamond.ac.uk
🎤 The DLS technical area
   beamline
🎤 Remote URI of this repository.
   https://gitlab.diamond.ac.uk/controls/containers/beamline/i04-deployment.git
🎤 Remote URI of the services repository that defines the IOCs and services,
   that this repository will track.
   https://gitlab.diamond.ac.uk/controls/containers/beamline/i04-services.git
🎤 The initial release of the services repository to track e.g. "2024.12.1" or "main"
   main
🎤 URL for centralized logging.
   DLS

[GDYendell]

🎤 URL for centralized logging.
DLS

What is this?

I think this is better. The only thing I would question is that it is halfway between being generic and being DLS-specific. I don't think this would be used by an external site as is, so we could either make it more convenient to use at DLS (more strict defaults instead of saying "at DLS ..."), or make it completely generic and then probably write some internal documentation to know what to use at DLS.

[marcelldls]

Im second guessing the use of "initial". Should updates to the release not be done by a copier update as best practice?

[gilesknap]

I dont think so - this is just what you will start with. I think that is what Initial means ?

[marcelldls]

Yes that is currently what is implied - but the question is should it? Should we not encourage updating the release rather through a copier update?

[gilesknap]

I feel that dirties the idea of what the template is for. But that's because I've not considered using this way before. But I think I prefer the idea that ec updates what we track, the template updates what the generic parts of the repo look like.

[marcelldls]

Thats fine. Its not used in more places so copier probably wont break. I imagine ec only updating on a service level though so its two different places

[gilesknap]

I don't think this would be used by an external site as is, so we could either make it more convenient to use at DLS (more strict defaults instead of saying "at DLS ..."), or make it completely generic and then probably write some internal documentation to know what to use at DLS.

I think this is a valid point and I considered switching to totally DLS specific for this for the moment. We could always make a new more generic version if anyone ever ends up adopting.

Making it DLS specific removes around half of the questions

But I have tried to make epics-containers site agnostic - I think it is fair to have 'at DLS we would use this' because it is a useful example to DLS people and outside users.

So I vote for sticking with what this PR has:

• mostly generic choices (but with namespaces and projects fixed as equal)
• hints that describe what we do at DLS

@GDYendell @marcelldls let me know if you feel differently.

[gilesknap]

🎤 URL for centralized logging.
DLS

What is this?

IT is the Graylog URL used when you type ec log-history xxxx

[marcelldls]

So I vote for sticking with what this PR has:

• mostly generic choices (but with namespaces and projects fixed as equal)
• hints that describe what we do at DLS

I agree that the PR does this. Its a decent middle ground. Changes LGTM

[gilesknap]

Thanks @marcelldls. Merging.