make service controls update version-controlled config

[rade]

Somebody at re:invent pointed out that there's a bit of a disconnect between the flux philosophy of updating version-controlled service configuration as well as instructing the orchestrator, and scope's "+/-" actions on a service, which only do the latter.

It's not clear how to address that.

• Make scope interact with service-conf repos like flux? That seems like a big leap for functionality that, in the grand scheme of things, is a fairly minor part of scope.
• Make scope interact with flux, at least in the context of Weave Cloud?
• Don't worry about it.
• Remove the service controls which make configuration changes.

[awh]

Remove the service controls which make configuration changes

... if we detect that you're using flux?

[foot]

The +|- actions have a nice playfulness to them. They feel kind of slow already so pushing through flux (probably?) won't help that.

• Add a ✏️ Write to k8s config button if (usingWC + usingFlux)
  • As flux has all the git writing machinery perhaps it could provide an HTTP endpoint for writing commits. :), like api.github.
• Flux could try to understand the intention of the commit in the repo, if the replicasets/othersets/cardinality of things haven't changed in the diff we're applying... read out the current k8s config from cluster and merge them as to preserve changes to the cluster made by other things too
  • breaks single source of truth model