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
It would be great if ARNs and IDs (eg. subnet IDs) could be provided instead of relying on the module to do data lookups (which may require changes to other infrastructure other than Kong).
The text was updated successfully, but these errors were encountered:
Curious the advantage of this approach. Relying on meta data/tags isn't intrusive setup changes ands offers flexibility when redeploying to a new VPC with different values.
For us, the advantage is not necessarily being tied to metadata/tags, but rather giving us the option on how/where to get the list from. If we want to pull from metadata for a particular deployment then we can do that lookup and pass in the IDs.
In most deployments, we create the VPC in the same stack that deploys Kong and its easier to take the output of the AWS VPC Module and just pass it right into this module than to ensure that all of the metadata lines up nicely.
It would be great if ARNs and IDs (eg. subnet IDs) could be provided instead of relying on the module to do data lookups (which may require changes to other infrastructure other than Kong).
The text was updated successfully, but these errors were encountered: