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

ApprovalRequired = Conditional : cherry-pick "only new attachments" should be approved #114

Open
Cupidazul opened this issue May 24, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Cupidazul
Copy link

We have ApprovalRequired implemented, therefore, new attachments should be manually approved.
The problem we are facing is that we have migrated TGW Routing Tables from one design to another, and wanted to implement a temporary freeze for new attachments, but in the meanwhile we would like to automatically accept re-associations for currently existing attachments (PROD attachments really need to move from one routing table to another with the least impact possible).

The issue for us is that, customers unaware of this freeze are continuing to create new attachments during the freeze period, we would like to cherry-pick only new attachments being created to continue to be approved, and at the same time, customers that are simply changing their Associate/Propagate VPC tags will be able to move around from one table to another quickly without having to wait for a manual approval.

Cherry picking OUs doesn't fit this purpose, because our customers may have more than one VPC in each OUs, and some may be already attached to our TGW, others may not.

@Cupidazul Cupidazul added the enhancement New feature or request label May 24, 2024
@dorrikh
Copy link
Member

dorrikh commented May 29, 2024

Thank you for your feedback, @Cupidazul. We are reviewing the request and will update the issue.

@dorrikh dorrikh assigned gockle and gsingh04 and unassigned gockle Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants