Merge branch 'master' into bigtable_replication

This commit is contained in:
Israel Herraiz 2022-12-30 11:28:12 +01:00 committed by GitHub
commit 4cccad9014
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 7 deletions

View File

@ -1,5 +1,6 @@
## 00-bootstrap
1. How to handle requests where automation, logging and/or billing export projects are not under organization but in different folders.
- Run bootstrap stage and let automation, logging and/or billing projects be created under organization.
- Run resource manager stage or any other custom stage which creates the folders where these projects will reside.
@ -7,17 +8,22 @@
- This step will move the projects from organization to the parent folders specificed.
## cicd
1. Why do we need two seperate ServiceAccounts when configuring cicd pipelines (cicd SA and IaC SA)
- Having seperate service accounts helps shutdown the pipeline incase of any issues and still keep IaC SA and ability to run terraform plan/apply manually.
- A pipeline can only generate a token that can get access to an SA. It cannot directly call a provider file to impersonate IaC SA.
- Having providers file that allows impersonation to IaC SA allows flexibility to run terraform manually or from CICD Pipelines.
<p align="center">
<img src="IaC_SA.png" alt="CICD SA and IaC SA">
</p>
![CICD SA and IaC SA](IaC_SA.png)
## Authenciation
1. If you are seeing "Permission Issues" when doing terraform apply and the identity with which you are running terraform has correct permissions;
run below command so that correct auth credentials are picked by ADC when terraform commands are executed
````bash
gcloud auth application-default login
````
Refer to [GCP Authentication](https://cloud.google.com/docs/authentication
) and [Terraform Provider](https://registry.terraform.io/providers/hashicorp/google/latest/docs/guides/provider_reference) for more information