John Mille
John Mille
I am having similar issues on my end. I set `DESCRIBE` and `DESCRIBE_CONFIGS` for all topics, all consumer groups (with a prefix though in the ACLs, such as `company.something`, for...
Just came across that one. Opened https://github.com/linkedin/Burrow/issues/707 just a while ago, being in the same situation.
I am yet to document what I did with [compose-x](https://labs.compose-x.io) but I will update here with what I used instead for confluent cloud.
```yaml services: my-app: {} x-alarms: high-cpu: Properties: Dimensions: service::my-app ``` or ```yaml services: my-app: x-alarms: high-cpu: Properties: {} # Dimensions etc. replaced with the service values ``` would resolve to...
AppMesh will need a deeper refactor to be far more agile and yet make it easy to add the envoy sidecar and ECS configuration for it. In the meatime, will...
Will need a schema update in ecs_composex_specs, but will simply add that as property.
In progress - modules will maintain the inventory of resources, new or lookup. Settings maintains the list of modules. So the settings.compose_content does not need to have the resources updated...
With the recent addition of `x-alarms` one could set that up manually. Alternatively, x-alarms could have a set of "well-known" alarms.
Another use-case that I have come across recently is for Fargate too (although applies to otherwise deployed on EC2 nodes) which is for Kafka related workloads which use RocksDB and...
To make matters worse some AWS resources tags are a mapping, not a list, or not called `Tags` either