Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cluster support #43

Open
scadu opened this issue Feb 7, 2022 · 0 comments
Open

Cluster support #43

scadu opened this issue Feb 7, 2022 · 0 comments

Comments

@scadu
Copy link

scadu commented Feb 7, 2022

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Slack Community

Describe the Feature

Possibility to define db-cluster in the aws_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 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant