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
First of all, thanks for putting together this module, it saves us a lot of time.
We are having an issue when we setup a new resource that depends on routing tables associated by your module when we want to destroy our infrastructure.
The issue is that prior we can delete our application resources, even though we have set a depends on the vpc.id , the vpc.aws_route_table_association.private and vpc.aws_route_table_association.public are deleted first, so all internal and external communication from and to our application is stopped which blocks us to terminate our applications accordingly.
We tried to find an output on your module that we could expose as "depends_on" for both vpc.aws_route_table_association.private and vpc.aws_route_table_association.public to our resource but it doesn't seem to exist yet.
The text was updated successfully, but these errors were encountered:
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.
Hi there,
First of all, thanks for putting together this module, it saves us a lot of time.
We are having an issue when we setup a new resource that depends on routing tables associated by your module when we want to destroy our infrastructure.
The issue is that prior we can delete our application resources, even though we have set a depends on the vpc.id , the vpc.aws_route_table_association.private and vpc.aws_route_table_association.public are deleted first, so all internal and external communication from and to our application is stopped which blocks us to terminate our applications accordingly.
We tried to find an output on your module that we could expose as "depends_on" for both vpc.aws_route_table_association.private and vpc.aws_route_table_association.public to our resource but it doesn't seem to exist yet.
The text was updated successfully, but these errors were encountered: