Commits on Mar 25, 2019

1. resource/aws_vpn_connection: Add transit_gateway_attachment_id attribute …

   Reference: #6884
   
   Only performs lookup when the VPN Connection has an associated Transit Gateway ID. I tried unsuccessfully to use a EC2 Transit Gateway shared via Resource Access Manager (RAM) in EC2 VPN Connection creation and it always returned the below error even after waiting for greater than 10 minutes and in the web console manually as well:
   
   ```
   InvalidTransitGatewayID.NotFound: The transitGateway ID 'tgw-XXXXXXXXX' does not exist
   ```
   
   This broken acceptance testing is omitted from this change request as it may not be functionality actually supported by EC2. If there is a working configuration with shared Transit Gateways, we may need to lean on additional feedback after this implementation to smooth over those issues.
   
   Output from acceptance testing:
   
   ```
   --- PASS: TestAccAWSVpnConnection_basic (617.58s)
   --- PASS: TestAccAWSVpnConnection_disappears (426.58s)
   --- PASS: TestAccAWSVpnConnection_importBasic (238.20s)
   --- PASS: TestAccAWSVpnConnection_TransitGatewayID (439.63s)
   --- PASS: TestAccAWSVpnConnection_tunnelOptions (269.52s)
   --- PASS: TestAccAWSVpnConnection_withoutStaticRoutes (195.55s)
   ```

   

   bflad committed Mar 25, 2019
   Configuration menu

   • View commit details
   • Copy full SHA for 55a59e8
   • Browse repository at this point

   Copy the full SHA

   55a59e8 View commit details

   Browse the repository at this point in the history