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

Sweepers: Extend CloudWatch Events sweepers to support custom Event Buses #15800

Closed
gdavison opened this issue Oct 22, 2020 · 2 comments
Closed
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/cloudwatch Issues and PRs that pertain to the cloudwatch service. stale Old or inactive issues managed by automation, if no further action taken these will get closed. technical-debt Addresses areas of the codebase that need refactoring or redesign.

Comments

@gdavison
Copy link
Contributor

gdavison commented Oct 22, 2020

Because the CloudWatch Events/EventBridge Bus, Permission, Rule, and Target resources are nested, all four need to support custom event buses before sweeping can be implemented for resources using a custom event bus

Affected Resource

  • aws_cloudwatch_event_bus
  • aws_cloudwatch_event_permission
  • aws_cloudwatch_event_rule
  • aws_cloudwatch_event_target

References

@gdavison gdavison added the enhancement Requests to existing resources that expand the functionality or scope. label Oct 22, 2020
@ghost ghost added service/cloudwatchevents service/cloudwatch Issues and PRs that pertain to the cloudwatch service. labels Oct 22, 2020
@gdavison gdavison added this to the Roadmap milestone Oct 22, 2020
@gdavison gdavison added technical-debt Addresses areas of the codebase that need refactoring or redesign. service/eventbridge and removed service/cloudwatch Issues and PRs that pertain to the cloudwatch service. labels Oct 22, 2020
@ghost ghost added the service/cloudwatch Issues and PRs that pertain to the cloudwatch service. label Oct 29, 2020
@breathingdust breathingdust removed this from the Roadmap milestone Nov 10, 2021
Copy link

github-actions bot commented Jan 1, 2024

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Jan 1, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 18, 2024
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/cloudwatch Issues and PRs that pertain to the cloudwatch service. stale Old or inactive issues managed by automation, if no further action taken these will get closed. technical-debt Addresses areas of the codebase that need refactoring or redesign.
Projects
None yet
Development

No branches or pull requests

3 participants