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
Copy file name to clipboardExpand all lines: CONTRIBUTING
+24-1Lines changed: 24 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -30,4 +30,27 @@ This project follows
30
30
All submissions, including submissions by project members, require review. We
31
31
use GitHub pull requests for this purpose. Consult
32
32
[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
33
-
information on using pull requests.
33
+
information on using pull requests.
34
+
35
+
### Linting and Formatting
36
+
37
+
Many of the files in the repository are checked against linting tools and static code analysis for secure coding practices. This workflow is triggered by [.github/workflows/lint.yaml](.github/workflows/lint.yaml), running multiple lint libraries in [Super-Linter](https://github.com/super-linter/super-linter) with the settings configured in [.github/linters/super-linter.env](.github/linters/super-linter.env)
38
+
39
+
1. To validate that your code passes these checks, use the following methods depending on your environment:
40
+
41
+
1. **GitHub Actions**: GitHub Actions will automatically run all configured checks when a PR is created or modified.
42
+
43
+
1. **Local**: You can manually trigger the tests in a docker container from your local environment with the following command:
44
+
45
+
```bash
46
+
./run_linters.sh
47
+
```
48
+
49
+
1. For issues that can be fixed automatically, you can automatically fix issues in your local environment with either of the following methods:
50
+
51
+
1. **Fix mode**: Run super-linter locally in fix mode by setting an environment variable to additionally run automatic fixes for the libraries configure
Copy file name to clipboardExpand all lines: gcmvsp/README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,3 @@
1
-
2
1
# Google Cloud Minimum Viable Secure Platform (GCMVSP)
3
2
4
3
This repository contains sample code to implement the set of terraform policies recommended by GMVSP.
@@ -8,16 +7,17 @@ This repository assumes you're already familiar with the [Organisation Policy Se
8
7
9
8
We recommend that new organizations should apply the full set of policies before creating other resources on Google Cloud. This creates a guardrail that resources cannot be created in violation of the organization policies.
10
9
11
-
For existing Google Cloud customers that have already created resources, implementing policies at the organization node can be risky, and might have existing resources in violation of the policy. In this scenario, we recommend that you use a combination of the following strategies:
12
-
-[Test organization policy changes with Policy Simulator](https://docs.cloud.google.com/policy-intelligence/docs/test-organization-policies)
13
-
-[Create an organization policy in dry-run mode](https://docs.cloud.google.com/resource-manager/docs/organization-policy/dry-run-policy)
14
-
- For legacy policies that don't support Policy Simulator or dry-run mode, enforce policies gradually by apply to a non-critical project or folder first to assess potential violations.
10
+
For existing Google Cloud customers that have already created resources, implementing policies at the organization node can be risky, and might have existing resources in violation of the policy. In this scenario, we recommend that you use a combination of the following strategies:
11
+
12
+
-[Test organization policy changes with Policy Simulator](https://docs.cloud.google.com/policy-intelligence/docs/test-organization-policies)
13
+
-[Create an organization policy in dry-run mode](https://docs.cloud.google.com/resource-manager/docs/organization-policy/dry-run-policy)
14
+
- For legacy policies that don't support Policy Simulator or dry-run mode, enforce policies gradually by apply to a non-critical project or folder first to assess potential violations.
15
15
16
16
## Quickstart
17
17
18
18
To deploy the Infrastructure-as-Code (IaC) resources using terraform, perform the follow steps:
19
19
20
-
1. Decide where in the [resource hierarchy](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy) (organization, folder, or project) you will apply organization policies.
20
+
1. Decide where in the [resource hierarchy](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy) (organization, folder, or project) you will apply organization policies.
21
21
22
22
1. This example code is deployed through Terraform using your own user identity. Your user identity needs the following [IAM Roles](https://cloud.google.com/iam/docs/roles-overview) on your organization, folder, or project:
23
23
@@ -46,9 +46,9 @@ To deploy the Infrastructure-as-Code (IaC) resources using terraform, perform th
46
46
47
47
1. Create a terraform.tfvars file with the following variables:
| parent_id | The ID of your your Google Cloud organization, folder, or project in the format organizations/123456789, folders/123456789, or projects/project-id.|
| parent_id | The ID of your your Google Cloud organization, folder, or project in the format organizations/123456789, folders/123456789, or projects/project-id. |
52
52
53
53
1. Initialize Terraform:
54
54
@@ -60,4 +60,4 @@ To deploy the Infrastructure-as-Code (IaC) resources using terraform, perform th
0 commit comments