01.06 Get access to stakeholders' version-control repositories and stakeholders' network

We deliver infrastructure and deployment for our customers. In doing this, we integrate our code into the rest of the project team. So, we often use the customer’s version-control repository. These days, it seems that most of our projects use Git, some use Subversion and then there’s been others such as Perforce and some others.
So, you will need to request read/write access to the customer’s version-control repositories. Typically, we create a pipeline folder in the application code version-control repository to host the code that creates the deployment production line. We also tend to create a separate repository for different infrastructure assets. We link these repositories together logically using fingerprints. In the examples you’ll see later, we track the commit SHAs from multiple Github repositories.
https://help.github.com/articles/adding-collaborators-to-a-personal-repository
Github - Add user

Accessing the stakeholders’ network

When creating the customer gateway (CGW,) you’ll need to know the IP address of the gateway device/VPN router and whether there is a BGP ASN (dynamic v static routing). When setting up routes, you’ll need to know the networks on their side that they will be routing.  You’ll also need to create the VPN connection and download the configuration for the proper VPN router. You’ll need to know the VPN router type to download the configuration for in order to give it to the stakeholders’ network engineers.