VPC peering

In this page, make sure that the team’s projects are under Emarsys>GAP>Attached resources folder if they were not created below it already.

If the projects are not under the said folder, you can move them individually by:

1. filtering on the project name
2. clicking on the three dots on the right of the project’s row and then clicking on settings in the opened bar
3. clicking on the Move button in the newly opened menu
4. navigating to the Emarsys>Emarsys GAP>Attached resources/Staging for the staging project or Emarsys>Emarsys GAP>Attached resources/Production for the production project
5. clicking on select and being happy of the project being moved by Google magic
6. double-check that the project was actually moved by Google magic, this might take 2-3 tries sometimes.

In this file, add the team’s projects’ names under staging and production respectively, following with the name of the team, similarly to how it is done with other projects. Take care of the -s and -p suffixes under staging and production objects in the file, also don’t forget the commas at the end of the line above.

The directories containing the Terraform entrypoints for this change are:

• environments/staging
• environments/production

Please note that to apply the changes to these entrypoint, you’ll need to be connected to the Emarsys VPN, and have the HTTPS_PROXY env variable set in your current shell session as described in the README.md file.