Implement ability to push config to agent(s)

[agardnerIT]

Along with the raw implementation, questions that need answered:

• Does this required a restart?
• Does the server request that the agent restarts and if so how is when the agent restarts controlled?
• Can the server force an agent restart? That seems dangerous!
• What happens if a config update fails (ie. user pushes bad update from server?)

[agardnerIT]

I've decided that it's just too dangerous to push config to an agent without the app having to do security checking, interpretation etc. That's not something I can maintain properly. Instead, the app will integrate with Git and create a PR.

Thus the app follows good GitOps principles and allows all the benefits of a Git-based workflow - reviews, approvals, rollbacks etc.

[ForkingFrenzy]

Isn't the whole point of OpAMP is to have the ability to push config to agent via the the server?

[agardnerIT]

Isn't the whole point of OpAMP is to have the ability to push config to agent via the the server?

Yes and no. OpAMP is a protocol. It's up to the implementors how they'd like to use the protocol.

I certainly see the attraction of pushing config, I'm just not sure I have the security awareness to do it right without opening people up to bugs / security issues. More than happy for assistance on this piece and if you do have the ability to push config safely, I'm more than happy to reconsider my stance.

That said, I aim for the server to have the ability to push config - in a way. I envisage a system where the user provides parameters to their Git repo & the server can thus open a PR for that config update. Then standard Git workflows take over - PR reviews and merges etc. So the end result is the same - the agent is updated - it just has some extra steps and isn't "live".

Again though, happy to reconsider this stance if / when I get more contributors