Open AlexanderFengFeng opened 3 years ago
The most important one AFAICS, is the datasource for google_access_context_manager_access_policy as this policy is a singleton.
A datasource for google_access_context_manager_access_level is not really required, as the id is the logical name that you gave it. In the example above, I can refer to the access level from any perimeter by specifying: accessPolicies/${data.google_access_context_manager_access_policy.access-policy.name}/accessLevels/chromeos_no_lock
as a id.
Service perimeters are not referenced in any other resource, so a datasource is not very relevant.
This needs to be evaluated if it is worth adding new data-sources for the google_access_context_manager
resources
Community Note
Description
It may be useful to have Data Source equivalents for some of the existing resources, particularly
google_access_context_manager_access_policy
,google_access_context_manager_access_level
, andgoogle_access_context_manager_service_perimeter
.For example, a
google_access_context_manager_access_policy
data source could be used to get the policy ID for an existing access policy based on the organization, meaning someone writing creating an access level or service perimeter for an existing policy could do so without having to find the policy ID (they would be finding it by the organization ID, which is arguably more accessible).New or Affected Resource(s)
Potential Terraform Configuration
b/359675471