Appliance Mode

[ratmav]

scaf currently suports a gitflow/argocd delivery model, which works well for services. some users will want an appliance-style deployment, which means argocd/gitops aren't available.

in these appliance style use cases, it makes sense to package the application using helm, then use the helm package to install the application on a target kubernetes cluster. so, it would be useful if scaf could:

• build, tag and push things like the application frontend, backend, etc. container images to an image registry, including new image versions.
• create a helm package for the application that uses the application images, and push the package to a helm repository, including new package versions.

in appliance mode, things like argocd and the terraform to manage the talos cluster would probably be unnecessary, so it'd be helpful to have a switch in the scaf to set the project "mode." for example:

# creates a default project. could be service only by default, or service and appliance. 
$ scaf new 

# explicitly create only an appliance.
$ scaf new --appliance

# explicitly create a service.
$ scaf new --service