I am +1 on all these concepts. This matches all of our anticipated
requirements for deployment of service configs, near instant changes, logging,
reporting, rollback and testing. I think the canary testing options need to be
fleshed out a bit more. There are a lot of different options
Moving this active debate into the mailing list.
-Jeremy makes a good point. We need a method for making restricting roles and
capabilities for lower tier staff that can create new users. Jeremy has
suggested a point system or a hierarchy. I think either of these would work if
applied
I second JvD, and I think the relevant goose version should be copied to a
location managed by the TC team.
This way, the will be no dependency of TC installs on an external,
uncontrollable source of data.
The issue was demonstrated a few months ago when the fancybox-2.1.5 source
code has moved.
