You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possibility to define db-cluster in the aws_db_event_subscriptionevent_type, so the module would support both database instances and clusters.
Expected Behavior
Ability to set either (or both?) var.db_instance_id and (a new parameter var.db_cluster_id.
If any of those variables are set, the module subscribes to those events and create alerts accordingly.
Use Case
In real life, where alerting is the most needed, usually, RDS clusters are deployed and not single instances.
Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Actually, it's described in the Expected Behavior section.
Alternatives Considered
None, I guess.
Additional Context
An MR that wasn't finished -- #27. Maybe we could start from there, but I guess adding the new variable var.db_cluster_id used as input for aws_db_event_subscription would be sufficient. Happy to open MR once we have a clear vision of how it could be implemented.
The text was updated successfully, but these errors were encountered:
Have a question? Please checkout our Slack Community or visit our Slack Archive.
Describe the Feature
Possibility to define
db-cluster
in theaws_db_event_subscription
event_type
, so the module would support both database instances and clusters.Expected Behavior
Ability to set either (or both?)
var.db_instance_id
and (a new parametervar.db_cluster_id
.If any of those variables are set, the module subscribes to those events and create alerts accordingly.
Use Case
In real life, where alerting is the most needed, usually, RDS clusters are deployed and not single instances.
Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Actually, it's described in the Expected Behavior section.
Alternatives Considered
None, I guess.
Additional Context
An MR that wasn't finished -- #27. Maybe we could start from there, but I guess adding the new variable
var.db_cluster_id
used as input foraws_db_event_subscription
would be sufficient. Happy to open MR once we have a clear vision of how it could be implemented.The text was updated successfully, but these errors were encountered: