Manage Memphis using REST/SDKs/GitOps

[yanivbh1]

A growing list of GitOps-driven management capabilities for Memphis -

REST

• [ ] Define Schemaverse schemas using YAML files
• [ ] Full Memphis initialization with a config file
• [ ] Dynamic state changes from a git repo
• [ ] Create users (asked by @ColTrez)
• [ ] Create stations
• [ ] Create integrations
• [ ] Purge all messages (Asked by @kchawla-pi)
• [ ] List all stations (Asked by @kchawla-pi)

SDK

• [ ] Purge all messages (Asked by @kchawla-pi)
• [ ] List all stations (Asked by @kchawla-pi)

[WarpWing]

Include dynamic state feature from git repo (Perhaps similar to ArgoCD where it constantly checks for changes in git repo state.) Create Ansible Role for Memphis(If needed, not much of a demand right now but useful for bare metal or hybrid cloud deployments afaik)

[yanivbh1]

Memphis is cloud-native by design, so bare metal is less of our aim. Regarding dynamic state - interesting.

[WarpWing]

That's a fair assessment for bare metal though I wouldn't surprised if later, people may want to mass deploy over SSH so Ansible may still be an option. I do like the idea of a dynamic state where it will poll or detect a state change in a GitHub repo, perhaps with a webhook or other notification system.

[kchawla-pi]

Another request:

When a station is created automatically via the Memphis().producer() and Memphis().consumer() methods, there is no way to specify retention type, though (sic) ack_time etc can be specified. It would be great if we could specify the retention_type a well.

[kchawla-pi]

Hi. It has been a few months. Any progress on my asks? Or are they already in and I overlooked them in the release notes?

[Cave-Johnson]

One to add, similarly to create stations it would be great to get an option to edit stations once created