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
When I was using ec2.Vpc.fromLookup with my RDS, it couldn't fetch the correct VPC and keep showing me vpc-12345 which is obviously not my VPC ID. However, after I removed the new rds.DatabaseCluster() creation code which only left Vpc.fromLookup, it backed to normal.
Is there anyone who also encountered the same issue on ec2.Vpc.fromLookup?
The workaround to me is to remove rds.DatabaseCluster first, then run cdk diff and add it back and run again.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered:
Specific subnet group names in an imported VPC may be missing
from the Dummy version of the imported VPC, leading to an exception
which aborts.
Turn the exception into a Construct error, which simply prevents deployment
of an incomplete construct instead of a complete abort.
Fixes#6115.
Specific subnet group names in an imported VPC may be missing
from the Dummy version of the imported VPC, leading to an exception
which aborts.
Turn the exception into a Construct error, which simply prevents deployment
of an incomplete construct instead of a complete abort.
Fixes#6115.
When I was using
ec2.Vpc.fromLookup
with my RDS, it couldn't fetch the correct VPC and keep showing mevpc-12345
which is obviously not my VPC ID. However, after I removed thenew rds.DatabaseCluster()
creation code which only left Vpc.fromLookup, it backed to normal.Reproduction Steps
My code:
And I ran
cdk diff
, I got this.➜ rds-aurora git:(develop) ✗ aws-vault exec staging -- cdk diff vpc-12345 Cluster requires at least 2 subnets, got 0 Subprocess exited with error 1
After I removed
new rds.DatabaseCluster
, it backed to normal.➜ rds-aurora git:(develop) ✗ aws-vault exec staging -- cdk diff vpc-12345 vpc-03eaf74111 Stack RdsAuroraStack There were no differences
Then I was trying to run again
➜ rds-aurora git:(develop) ✗ aws-vault exec staging -- cdk diff vpc-03eaf74111 Stack RdsAuroraStack There were no differences
At lastly, I added the rds backed. It becomes normal.
➜ rds-aurora git:(develop) ✗ aws-vault exec staging -- cdk diff vpc-03eaf74111 Stack RdsAuroraStack Resources [+] AWS::RDS::DBSubnetGroup rds/Subnets rdsSubnet111 [+] AWS::RDS::DBCluster rds rds111 [+] AWS::RDS::DBInstance rds/Instance1 rdsInstance111 [+] AWS::RDS::DBInstance rds/Instance2 rdsInstance111
Environment
Other
Is there anyone who also encountered the same issue on
ec2.Vpc.fromLookup
?The workaround to me is to remove
rds.DatabaseCluster
first, then runcdk diff
and add it back and run again.This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: