Google Cloud Healthcare Consent Store
This page shows how to write Terraform for Cloud Healthcare Consent Store and write them securely.
The Consent Store in Cloud Healthcare can be configured in Terraform with the resource name
google_healthcare_consent_store. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
datasetrequired - string
Identifies the dataset addressed by this request. Must be in the format 'projects/[project]/locations/[location]/datasets/[dataset]'
default_consent_ttloptional - string
Default time to live for consents in this store. Must be at least 24 hours. Updating this field will not affect the expiration time of existing consents. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s".
enable_consent_create_on_updateoptional - bool
If true, [consents.patch][google.cloud.healthcare.v1.consent.UpdateConsent] creates the consent if it does not already exist.
User-supplied key-value pairs used to organize Consent stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: '[p[Ll]p[Lo]][p[Ll]p[Lo]p[N]_-][0,62]' Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: '[p[Ll]p[Lo]p[N]_-][0,63]' No more than 64 labels can be associated with a given store. An object containing a list of "key": value pairs. Example: [ "name": "wrench", "mass": "1.3kg", "count": "3" ].
namerequired - string
The name of this ConsentStore, for example: "consent1"
Explanation in Terraform Registry
The Consent Management API is a tool for tracking user consents and the documentation associated with the consents. To get more information about ConsentStore, see: