Add ACM resources, fix file name bug

docs/resources/google_access_context_manager_access_policies.md

@@ -0,0 +1,32 @@
+---
+title: About the google_access_context_manager_access_policies resource
+platform: gcp
+---
+
+## Syntax
+A `google_access_context_manager_access_policies` is used to test a Google AccessPolicy resource
+
+## Examples
+```
+
+describe google_access_context_manager_access_policies(org_id: '190694428152') do
+  its('count') { should be >= 1 }
+  its('titles') { should include 'policytitle' }
+end
+```
+
+## Properties
+Properties that can be accessed from the `google_access_context_manager_access_policies` resource:
+
+See [google_access_context_manager_access_policy.md](google_access_context_manager_access_policy.md) for more detailed information
+  * `names`: an array of `google_access_context_manager_access_policy` name
+  * `create_times`: an array of `google_access_context_manager_access_policy` create_time
+  * `update_times`: an array of `google_access_context_manager_access_policy` update_time
+  * `parents`: an array of `google_access_context_manager_access_policy` parent
+  * `titles`: an array of `google_access_context_manager_access_policy` title
+
+## Filter Criteria
+This resource supports all of the above properties as filter criteria, which can be used
+with `where` as a block or a method.
+
+## GCP Permissions

docs/resources/google_access_context_manager_access_policy.md

@@ -0,0 +1,38 @@
+---
+title: About the google_access_context_manager_access_policy resource
+platform: gcp
+---
+
+## Syntax
+A `google_access_context_manager_access_policy` is used to test a Google AccessPolicy resource
+
+## Examples
+```
+
+describe.one do
+  google_access_context_manager_access_policies(org_id: '190694428152').names.each do |policy_name|
+    describe google_access_context_manager_access_policy(name: policy_name) do
+      it { should exist }
+      its('title') { should cmp 'policytitle' }
+      its('parent') { should match '190694428152' }
+    end
+  end
+end
+```
+
+## Properties
+Properties that can be accessed from the `google_access_context_manager_access_policy` resource:
+
+
+  * `name`: Resource name of the AccessPolicy. Format: accessPolicies/{policy_id}
+
+  * `create_time`: Time the AccessPolicy was created in UTC.
+
+  * `update_time`: Time the AccessPolicy was updated in UTC.
+
+  * `parent`: The parent of this AccessPolicy in the Cloud Resource Hierarchy. Format: organizations/{organization_id}
+
+  * `title`: Human readable title. Does not affect behavior.
+
+
+## GCP Permissions

docs/resources/google_access_context_manager_service_perimeter.md

@@ -0,0 +1,50 @@
+---
+title: About the google_access_context_manager_service_perimeter resource
+platform: gcp
+---
+
+## Syntax
+A `google_access_context_manager_service_perimeter` is used to test a Google ServicePerimeter resource
+
+## Examples
+```
+
+describe.one do
+  google_access_context_manager_access_policies(org_id: '190694428152').names.each do |policy_name|
+    describe google_access_context_manager_service_perimeter(policy_name: policy_name, name: 'restrict_all') do
+      it { should exist }
+      its('title') { should cmp 'restrict_all' }
+      its('status.restricted_services') { should include 'storage.googleapis.com' }
+    end
+  end
+end
+```
+
+## Properties
+Properties that can be accessed from the `google_access_context_manager_service_perimeter` resource:
+
+
+  * `title`: Human readable title. Must be unique within the Policy.
+
+  * `description`: Description of the ServicePerimeter and its use. Does not affect behavior.
+
+  * `create_time`: Time the AccessPolicy was created in UTC.
+
+  * `update_time`: Time the AccessPolicy was updated in UTC.
+
+  * `perimeter_type`: Specifies the type of the Perimeter. There are two types: regular and bridge. Regular Service Perimeter contains resources, access levels, and restricted services. Every resource can be in at most ONE regular Service Perimeter.  In addition to being in a regular service perimeter, a resource can also be in zero or more perimeter bridges. A perimeter bridge only contains resources. Cross project operations are permitted if all effected resources share some perimeter (whether bridge or regular). Perimeter Bridge does not contain access levels or services: those are governed entirely by the regular perimeter that resource is in.  Perimeter Bridges are typically useful when building more complex topologies with many independent perimeters that need to share some data with a common perimeter, but should not be able to share data among themselves.
+
+  * `status`: ServicePerimeter configuration. Specifies sets of resources, restricted services and access levels that determine perimeter content and boundaries.
+
+    * `resources`: A list of GCP resources that are inside of the service perimeter. Currently only projects are allowed. Format: projects/{project_number}
+
+    * `access_levels`: A list of AccessLevel resource names that allow resources within the ServicePerimeter to be accessed from the internet. AccessLevels listed must be in the same policy as this ServicePerimeter. Referencing a nonexistent AccessLevel is a syntax error. If no AccessLevel names are listed, resources within the perimeter can only be accessed via GCP calls with request origins within the perimeter. For Service Perimeter Bridge, must be empty.  Format: accessPolicies/{policy_id}/accessLevels/{access_level_name}
+
+    * `restricted_services`: GCP services that are subject to the Service Perimeter restrictions. Must contain a list of services. For example, if `storage.googleapis.com` is specified, access to the storage buckets inside the perimeter must meet the perimeter's access restrictions.
+
+  * `parent`: The AccessPolicy this ServicePerimeter lives in. Format: accessPolicies/{policy_id}
+
+  * `name`: Resource name for the ServicePerimeter. The short_name component must begin with a letter and only include alphanumeric and '_'. Format: accessPolicies/{policy_id}/servicePerimeters/{short_name}
+
+
+## GCP Permissions

docs/resources/google_access_context_manager_service_perimeters.md

@@ -0,0 +1,39 @@
+---
+title: About the google_access_context_manager_service_perimeters resource
+platform: gcp
+---
+
+## Syntax
+A `google_access_context_manager_service_perimeters` is used to test a Google ServicePerimeter resource
+
+## Examples
+```
+
+describe.one do
+  google_access_context_manager_access_policies(org_id: '190694428152').names.each do |policy_name|
+    describe google_access_context_manager_service_perimeters(policy_name: policy_name) do
+      its('names') { should include 'restrict_all' }
+      its('titles') { should include 'restrict_all' }
+    end
+  end
+end
+```
+
+## Properties
+Properties that can be accessed from the `google_access_context_manager_service_perimeters` resource:
+
+See [google_access_context_manager_service_perimeter.md](google_access_context_manager_service_perimeter.md) for more detailed information
+  * `titles`: an array of `google_access_context_manager_service_perimeter` title
+  * `descriptions`: an array of `google_access_context_manager_service_perimeter` description
+  * `create_times`: an array of `google_access_context_manager_service_perimeter` create_time
+  * `update_times`: an array of `google_access_context_manager_service_perimeter` update_time
+  * `perimeter_types`: an array of `google_access_context_manager_service_perimeter` perimeter_type
+  * `statuses`: an array of `google_access_context_manager_service_perimeter` status
+  * `parents`: an array of `google_access_context_manager_service_perimeter` parent
+  * `names`: an array of `google_access_context_manager_service_perimeter` name
+
+## Filter Criteria
+This resource supports all of the above properties as filter criteria, which can be used
+with `where` as a block or a method.
+
+## GCP Permissions