Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
google-native.binaryauthorization/v1.getPolicy
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
Gets a platform policy. Returns NOT_FOUND
if the policy doesn’t exist.
Using getPolicy
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getPolicy(args: GetPolicyArgs, opts?: InvokeOptions): Promise<GetPolicyResult>
function getPolicyOutput(args: GetPolicyOutputArgs, opts?: InvokeOptions): Output<GetPolicyResult>
def get_policy(platform_id: Optional[str] = None,
policy_id: Optional[str] = None,
project: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetPolicyResult
def get_policy_output(platform_id: Optional[pulumi.Input[str]] = None,
policy_id: Optional[pulumi.Input[str]] = None,
project: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetPolicyResult]
func LookupPolicy(ctx *Context, args *LookupPolicyArgs, opts ...InvokeOption) (*LookupPolicyResult, error)
func LookupPolicyOutput(ctx *Context, args *LookupPolicyOutputArgs, opts ...InvokeOption) LookupPolicyResultOutput
> Note: This function is named LookupPolicy
in the Go SDK.
public static class GetPolicy
{
public static Task<GetPolicyResult> InvokeAsync(GetPolicyArgs args, InvokeOptions? opts = null)
public static Output<GetPolicyResult> Invoke(GetPolicyInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetPolicyResult> getPolicy(GetPolicyArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:binaryauthorization/v1:getPolicy
arguments:
# arguments dictionary
The following arguments are supported:
- Platform
Id string - Policy
Id string - Project string
- Platform
Id string - Policy
Id string - Project string
- platform
Id String - policy
Id String - project String
- platform
Id string - policy
Id string - project string
- platform_
id str - policy_
id str - project str
- platform
Id String - policy
Id String - project String
getPolicy Result
The following output properties are available:
- Description string
- Optional. A description comment about the policy.
- Gke
Policy Pulumi.Google Native. Binary Authorization. V1. Outputs. Gke Policy Response - Optional. GKE platform-specific policy.
- Name string
- The relative resource name of the Binary Authorization platform policy, in the form of
projects/*/platforms/*/policies/*
. - Update
Time string - Time when the policy was last updated.
- Description string
- Optional. A description comment about the policy.
- Gke
Policy GkePolicy Response - Optional. GKE platform-specific policy.
- Name string
- The relative resource name of the Binary Authorization platform policy, in the form of
projects/*/platforms/*/policies/*
. - Update
Time string - Time when the policy was last updated.
- description String
- Optional. A description comment about the policy.
- gke
Policy GkePolicy Response - Optional. GKE platform-specific policy.
- name String
- The relative resource name of the Binary Authorization platform policy, in the form of
projects/*/platforms/*/policies/*
. - update
Time String - Time when the policy was last updated.
- description string
- Optional. A description comment about the policy.
- gke
Policy GkePolicy Response - Optional. GKE platform-specific policy.
- name string
- The relative resource name of the Binary Authorization platform policy, in the form of
projects/*/platforms/*/policies/*
. - update
Time string - Time when the policy was last updated.
- description str
- Optional. A description comment about the policy.
- gke_
policy GkePolicy Response - Optional. GKE platform-specific policy.
- name str
- The relative resource name of the Binary Authorization platform policy, in the form of
projects/*/platforms/*/policies/*
. - update_
time str - Time when the policy was last updated.
- description String
- Optional. A description comment about the policy.
- gke
Policy Property Map - Optional. GKE platform-specific policy.
- name String
- The relative resource name of the Binary Authorization platform policy, in the form of
projects/*/platforms/*/policies/*
. - update
Time String - Time when the policy was last updated.
Supporting Types
AttestationAuthenticatorResponse
- Display
Name string - Optional. A user-provided name for this
AttestationAuthenticator
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - Pkix
Public Pulumi.Key Set Google Native. Binary Authorization. V1. Inputs. Pkix Public Key Set Response - Optional. A set of raw PKIX SubjectPublicKeyInfo format public keys. If any public key in the set validates the attestation signature, then the signature is considered authenticated (i.e. any one key is sufficient to authenticate).
- Display
Name string - Optional. A user-provided name for this
AttestationAuthenticator
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - Pkix
Public PkixKey Set Public Key Set Response - Optional. A set of raw PKIX SubjectPublicKeyInfo format public keys. If any public key in the set validates the attestation signature, then the signature is considered authenticated (i.e. any one key is sufficient to authenticate).
- display
Name String - Optional. A user-provided name for this
AttestationAuthenticator
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - pkix
Public PkixKey Set Public Key Set Response - Optional. A set of raw PKIX SubjectPublicKeyInfo format public keys. If any public key in the set validates the attestation signature, then the signature is considered authenticated (i.e. any one key is sufficient to authenticate).
- display
Name string - Optional. A user-provided name for this
AttestationAuthenticator
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - pkix
Public PkixKey Set Public Key Set Response - Optional. A set of raw PKIX SubjectPublicKeyInfo format public keys. If any public key in the set validates the attestation signature, then the signature is considered authenticated (i.e. any one key is sufficient to authenticate).
- display_
name str - Optional. A user-provided name for this
AttestationAuthenticator
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - pkix_
public_ Pkixkey_ set Public Key Set Response - Optional. A set of raw PKIX SubjectPublicKeyInfo format public keys. If any public key in the set validates the attestation signature, then the signature is considered authenticated (i.e. any one key is sufficient to authenticate).
- display
Name String - Optional. A user-provided name for this
AttestationAuthenticator
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - pkix
Public Property MapKey Set - Optional. A set of raw PKIX SubjectPublicKeyInfo format public keys. If any public key in the set validates the attestation signature, then the signature is considered authenticated (i.e. any one key is sufficient to authenticate).
AttestationSourceResponse
- Container
Analysis List<string>Attestation Projects - The IDs of the GCP projects storing the SLSA attestations as Container Analysis Occurrences.
- Container
Analysis []stringAttestation Projects - The IDs of the GCP projects storing the SLSA attestations as Container Analysis Occurrences.
- container
Analysis List<String>Attestation Projects - The IDs of the GCP projects storing the SLSA attestations as Container Analysis Occurrences.
- container
Analysis string[]Attestation Projects - The IDs of the GCP projects storing the SLSA attestations as Container Analysis Occurrences.
- container_
analysis_ Sequence[str]attestation_ projects - The IDs of the GCP projects storing the SLSA attestations as Container Analysis Occurrences.
- container
Analysis List<String>Attestation Projects - The IDs of the GCP projects storing the SLSA attestations as Container Analysis Occurrences.
CheckResponse
- Always
Deny bool - Optional. A special-case check that always denies. Note that this still only applies when the scope of the
CheckSet
applies and the image isn't exempted by an image allowlist. This check is primarily useful for testing, or to set the default behavior for all unmatched scopes to "deny". - Display
Name string - Optional. A user-provided name for this check. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results.
- Image
Allowlist Pulumi.Google Native. Binary Authorization. V1. Inputs. Image Allowlist Response - Optional. Images exempted from this check. If any of the patterns match the image url, the check will not be evaluated.
- Image
Freshness Pulumi.Check Google Native. Binary Authorization. V1. Inputs. Image Freshness Check Response - Optional. Require that an image is no older than a configured expiration time. Image age is determined by its upload time.
- Simple
Signing Pulumi.Attestation Check Google Native. Binary Authorization. V1. Inputs. Simple Signing Attestation Check Response - Optional. Require a SimpleSigning-type attestation for every image in the deployment.
- Slsa
Check Pulumi.Google Native. Binary Authorization. V1. Inputs. Slsa Check Response - Optional. Require that an image was built by a trusted builder (such as Google Cloud Build), meets requirements for Supply chain Levels for Software Artifacts (SLSA), and was built from a trusted source code repostitory.
- Trusted
Directory Pulumi.Check Google Native. Binary Authorization. V1. Inputs. Trusted Directory Check Response - Optional. Require that an image lives in a trusted directory.
- Vulnerability
Check Pulumi.Google Native. Binary Authorization. V1. Inputs. Vulnerability Check Response - Optional. Require that an image does not contain vulnerabilities that violate the configured rules, such as based on severity levels.
- Always
Deny bool - Optional. A special-case check that always denies. Note that this still only applies when the scope of the
CheckSet
applies and the image isn't exempted by an image allowlist. This check is primarily useful for testing, or to set the default behavior for all unmatched scopes to "deny". - Display
Name string - Optional. A user-provided name for this check. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results.
- Image
Allowlist ImageAllowlist Response - Optional. Images exempted from this check. If any of the patterns match the image url, the check will not be evaluated.
- Image
Freshness ImageCheck Freshness Check Response - Optional. Require that an image is no older than a configured expiration time. Image age is determined by its upload time.
- Simple
Signing SimpleAttestation Check Signing Attestation Check Response - Optional. Require a SimpleSigning-type attestation for every image in the deployment.
- Slsa
Check SlsaCheck Response - Optional. Require that an image was built by a trusted builder (such as Google Cloud Build), meets requirements for Supply chain Levels for Software Artifacts (SLSA), and was built from a trusted source code repostitory.
- Trusted
Directory TrustedCheck Directory Check Response - Optional. Require that an image lives in a trusted directory.
- Vulnerability
Check VulnerabilityCheck Response - Optional. Require that an image does not contain vulnerabilities that violate the configured rules, such as based on severity levels.
- always
Deny Boolean - Optional. A special-case check that always denies. Note that this still only applies when the scope of the
CheckSet
applies and the image isn't exempted by an image allowlist. This check is primarily useful for testing, or to set the default behavior for all unmatched scopes to "deny". - display
Name String - Optional. A user-provided name for this check. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results.
- image
Allowlist ImageAllowlist Response - Optional. Images exempted from this check. If any of the patterns match the image url, the check will not be evaluated.
- image
Freshness ImageCheck Freshness Check Response - Optional. Require that an image is no older than a configured expiration time. Image age is determined by its upload time.
- simple
Signing SimpleAttestation Check Signing Attestation Check Response - Optional. Require a SimpleSigning-type attestation for every image in the deployment.
- slsa
Check SlsaCheck Response - Optional. Require that an image was built by a trusted builder (such as Google Cloud Build), meets requirements for Supply chain Levels for Software Artifacts (SLSA), and was built from a trusted source code repostitory.
- trusted
Directory TrustedCheck Directory Check Response - Optional. Require that an image lives in a trusted directory.
- vulnerability
Check VulnerabilityCheck Response - Optional. Require that an image does not contain vulnerabilities that violate the configured rules, such as based on severity levels.
- always
Deny boolean - Optional. A special-case check that always denies. Note that this still only applies when the scope of the
CheckSet
applies and the image isn't exempted by an image allowlist. This check is primarily useful for testing, or to set the default behavior for all unmatched scopes to "deny". - display
Name string - Optional. A user-provided name for this check. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results.
- image
Allowlist ImageAllowlist Response - Optional. Images exempted from this check. If any of the patterns match the image url, the check will not be evaluated.
- image
Freshness ImageCheck Freshness Check Response - Optional. Require that an image is no older than a configured expiration time. Image age is determined by its upload time.
- simple
Signing SimpleAttestation Check Signing Attestation Check Response - Optional. Require a SimpleSigning-type attestation for every image in the deployment.
- slsa
Check SlsaCheck Response - Optional. Require that an image was built by a trusted builder (such as Google Cloud Build), meets requirements for Supply chain Levels for Software Artifacts (SLSA), and was built from a trusted source code repostitory.
- trusted
Directory TrustedCheck Directory Check Response - Optional. Require that an image lives in a trusted directory.
- vulnerability
Check VulnerabilityCheck Response - Optional. Require that an image does not contain vulnerabilities that violate the configured rules, such as based on severity levels.
- always_
deny bool - Optional. A special-case check that always denies. Note that this still only applies when the scope of the
CheckSet
applies and the image isn't exempted by an image allowlist. This check is primarily useful for testing, or to set the default behavior for all unmatched scopes to "deny". - display_
name str - Optional. A user-provided name for this check. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results.
- image_
allowlist ImageAllowlist Response - Optional. Images exempted from this check. If any of the patterns match the image url, the check will not be evaluated.
- image_
freshness_ Imagecheck Freshness Check Response - Optional. Require that an image is no older than a configured expiration time. Image age is determined by its upload time.
- simple_
signing_ Simpleattestation_ check Signing Attestation Check Response - Optional. Require a SimpleSigning-type attestation for every image in the deployment.
- slsa_
check SlsaCheck Response - Optional. Require that an image was built by a trusted builder (such as Google Cloud Build), meets requirements for Supply chain Levels for Software Artifacts (SLSA), and was built from a trusted source code repostitory.
- trusted_
directory_ Trustedcheck Directory Check Response - Optional. Require that an image lives in a trusted directory.
- vulnerability_
check VulnerabilityCheck Response - Optional. Require that an image does not contain vulnerabilities that violate the configured rules, such as based on severity levels.
- always
Deny Boolean - Optional. A special-case check that always denies. Note that this still only applies when the scope of the
CheckSet
applies and the image isn't exempted by an image allowlist. This check is primarily useful for testing, or to set the default behavior for all unmatched scopes to "deny". - display
Name String - Optional. A user-provided name for this check. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results.
- image
Allowlist Property Map - Optional. Images exempted from this check. If any of the patterns match the image url, the check will not be evaluated.
- image
Freshness Property MapCheck - Optional. Require that an image is no older than a configured expiration time. Image age is determined by its upload time.
- simple
Signing Property MapAttestation Check - Optional. Require a SimpleSigning-type attestation for every image in the deployment.
- slsa
Check Property Map - Optional. Require that an image was built by a trusted builder (such as Google Cloud Build), meets requirements for Supply chain Levels for Software Artifacts (SLSA), and was built from a trusted source code repostitory.
- trusted
Directory Property MapCheck - Optional. Require that an image lives in a trusted directory.
- vulnerability
Check Property Map - Optional. Require that an image does not contain vulnerabilities that violate the configured rules, such as based on severity levels.
CheckSetResponse
- Checks
List<Pulumi.
Google Native. Binary Authorization. V1. Inputs. Check Response> - Optional. The checks to apply. The ultimate result of evaluating the check set will be "allow" if and only if every check in
checks
evaluates to "allow". Ifchecks
is empty, the default behavior is "always allow". - Display
Name string - Optional. A user-provided name for this
CheckSet
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - Image
Allowlist Pulumi.Google Native. Binary Authorization. V1. Inputs. Image Allowlist Response - Optional. Images exempted from this
CheckSet
. If any of the patterns match the image being evaluated, no checks in theCheckSet
will be evaluated. - Scope
Pulumi.
Google Native. Binary Authorization. V1. Inputs. Scope Response - Optional. The scope to which this
CheckSet
applies. If unset or an empty string (the default), applies to all namespaces and service accounts. See theScope
message documentation for details on scoping rules.
- Checks
[]Check
Response - Optional. The checks to apply. The ultimate result of evaluating the check set will be "allow" if and only if every check in
checks
evaluates to "allow". Ifchecks
is empty, the default behavior is "always allow". - Display
Name string - Optional. A user-provided name for this
CheckSet
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - Image
Allowlist ImageAllowlist Response - Optional. Images exempted from this
CheckSet
. If any of the patterns match the image being evaluated, no checks in theCheckSet
will be evaluated. - Scope
Scope
Response - Optional. The scope to which this
CheckSet
applies. If unset or an empty string (the default), applies to all namespaces and service accounts. See theScope
message documentation for details on scoping rules.
- checks
List<Check
Response> - Optional. The checks to apply. The ultimate result of evaluating the check set will be "allow" if and only if every check in
checks
evaluates to "allow". Ifchecks
is empty, the default behavior is "always allow". - display
Name String - Optional. A user-provided name for this
CheckSet
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - image
Allowlist ImageAllowlist Response - Optional. Images exempted from this
CheckSet
. If any of the patterns match the image being evaluated, no checks in theCheckSet
will be evaluated. - scope
Scope
Response - Optional. The scope to which this
CheckSet
applies. If unset or an empty string (the default), applies to all namespaces and service accounts. See theScope
message documentation for details on scoping rules.
- checks
Check
Response[] - Optional. The checks to apply. The ultimate result of evaluating the check set will be "allow" if and only if every check in
checks
evaluates to "allow". Ifchecks
is empty, the default behavior is "always allow". - display
Name string - Optional. A user-provided name for this
CheckSet
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - image
Allowlist ImageAllowlist Response - Optional. Images exempted from this
CheckSet
. If any of the patterns match the image being evaluated, no checks in theCheckSet
will be evaluated. - scope
Scope
Response - Optional. The scope to which this
CheckSet
applies. If unset or an empty string (the default), applies to all namespaces and service accounts. See theScope
message documentation for details on scoping rules.
- checks
Sequence[Check
Response] - Optional. The checks to apply. The ultimate result of evaluating the check set will be "allow" if and only if every check in
checks
evaluates to "allow". Ifchecks
is empty, the default behavior is "always allow". - display_
name str - Optional. A user-provided name for this
CheckSet
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - image_
allowlist ImageAllowlist Response - Optional. Images exempted from this
CheckSet
. If any of the patterns match the image being evaluated, no checks in theCheckSet
will be evaluated. - scope
Scope
Response - Optional. The scope to which this
CheckSet
applies. If unset or an empty string (the default), applies to all namespaces and service accounts. See theScope
message documentation for details on scoping rules.
- checks List<Property Map>
- Optional. The checks to apply. The ultimate result of evaluating the check set will be "allow" if and only if every check in
checks
evaluates to "allow". Ifchecks
is empty, the default behavior is "always allow". - display
Name String - Optional. A user-provided name for this
CheckSet
. This field has no effect on the policy evaluation behavior except to improve readability of messages in evaluation results. - image
Allowlist Property Map - Optional. Images exempted from this
CheckSet
. If any of the patterns match the image being evaluated, no checks in theCheckSet
will be evaluated. - scope Property Map
- Optional. The scope to which this
CheckSet
applies. If unset or an empty string (the default), applies to all namespaces and service accounts. See theScope
message documentation for details on scoping rules.
GkePolicyResponse
- Check
Sets List<Pulumi.Google Native. Binary Authorization. V1. Inputs. Check Set Response> - Optional. The
CheckSet
objects to apply, scoped by namespace or namespace and service account. Exactly oneCheckSet
will be evaluated for a given Pod (unless the list is empty, in which case the behavior is "always allow"). If multipleCheckSet
objects have scopes that match the namespace and service account of the Pod being evaluated, only theCheckSet
with the MOST SPECIFIC scope will match.CheckSet
objects must be listed in order of decreasing specificity, i.e. if a scope matches a given service account (which must include the namespace), it must come before aCheckSet
with a scope matching just that namespace. This property is enforced by server-side validation. The purpose of this restriction is to ensure that if more than oneCheckSet
matches a given Pod, theCheckSet
that will be evaluated will always be the first in the list to match (because if any other matches, it must be less specific). Ifcheck_sets
is empty, the default behavior is to allow all images. Ifcheck_sets
is non-empty, the lastcheck_sets
entry must always be aCheckSet
with no scope set, i.e. a catchall to handle any situation not caught by the precedingCheckSet
objects. - Image
Allowlist Pulumi.Google Native. Binary Authorization. V1. Inputs. Image Allowlist Response - Optional. Images exempted from this policy. If any of the patterns match the image being evaluated, the rest of the policy will not be evaluated.
- Check
Sets []CheckSet Response - Optional. The
CheckSet
objects to apply, scoped by namespace or namespace and service account. Exactly oneCheckSet
will be evaluated for a given Pod (unless the list is empty, in which case the behavior is "always allow"). If multipleCheckSet
objects have scopes that match the namespace and service account of the Pod being evaluated, only theCheckSet
with the MOST SPECIFIC scope will match.CheckSet
objects must be listed in order of decreasing specificity, i.e. if a scope matches a given service account (which must include the namespace), it must come before aCheckSet
with a scope matching just that namespace. This property is enforced by server-side validation. The purpose of this restriction is to ensure that if more than oneCheckSet
matches a given Pod, theCheckSet
that will be evaluated will always be the first in the list to match (because if any other matches, it must be less specific). Ifcheck_sets
is empty, the default behavior is to allow all images. Ifcheck_sets
is non-empty, the lastcheck_sets
entry must always be aCheckSet
with no scope set, i.e. a catchall to handle any situation not caught by the precedingCheckSet
objects. - Image
Allowlist ImageAllowlist Response - Optional. Images exempted from this policy. If any of the patterns match the image being evaluated, the rest of the policy will not be evaluated.
- check
Sets List<CheckSet Response> - Optional. The
CheckSet
objects to apply, scoped by namespace or namespace and service account. Exactly oneCheckSet
will be evaluated for a given Pod (unless the list is empty, in which case the behavior is "always allow"). If multipleCheckSet
objects have scopes that match the namespace and service account of the Pod being evaluated, only theCheckSet
with the MOST SPECIFIC scope will match.CheckSet
objects must be listed in order of decreasing specificity, i.e. if a scope matches a given service account (which must include the namespace), it must come before aCheckSet
with a scope matching just that namespace. This property is enforced by server-side validation. The purpose of this restriction is to ensure that if more than oneCheckSet
matches a given Pod, theCheckSet
that will be evaluated will always be the first in the list to match (because if any other matches, it must be less specific). Ifcheck_sets
is empty, the default behavior is to allow all images. Ifcheck_sets
is non-empty, the lastcheck_sets
entry must always be aCheckSet
with no scope set, i.e. a catchall to handle any situation not caught by the precedingCheckSet
objects. - image
Allowlist ImageAllowlist Response - Optional. Images exempted from this policy. If any of the patterns match the image being evaluated, the rest of the policy will not be evaluated.
- check
Sets CheckSet Response[] - Optional. The
CheckSet
objects to apply, scoped by namespace or namespace and service account. Exactly oneCheckSet
will be evaluated for a given Pod (unless the list is empty, in which case the behavior is "always allow"). If multipleCheckSet
objects have scopes that match the namespace and service account of the Pod being evaluated, only theCheckSet
with the MOST SPECIFIC scope will match.CheckSet
objects must be listed in order of decreasing specificity, i.e. if a scope matches a given service account (which must include the namespace), it must come before aCheckSet
with a scope matching just that namespace. This property is enforced by server-side validation. The purpose of this restriction is to ensure that if more than oneCheckSet
matches a given Pod, theCheckSet
that will be evaluated will always be the first in the list to match (because if any other matches, it must be less specific). Ifcheck_sets
is empty, the default behavior is to allow all images. Ifcheck_sets
is non-empty, the lastcheck_sets
entry must always be aCheckSet
with no scope set, i.e. a catchall to handle any situation not caught by the precedingCheckSet
objects. - image
Allowlist ImageAllowlist Response - Optional. Images exempted from this policy. If any of the patterns match the image being evaluated, the rest of the policy will not be evaluated.
- check_
sets Sequence[CheckSet Response] - Optional. The
CheckSet
objects to apply, scoped by namespace or namespace and service account. Exactly oneCheckSet
will be evaluated for a given Pod (unless the list is empty, in which case the behavior is "always allow"). If multipleCheckSet
objects have scopes that match the namespace and service account of the Pod being evaluated, only theCheckSet
with the MOST SPECIFIC scope will match.CheckSet
objects must be listed in order of decreasing specificity, i.e. if a scope matches a given service account (which must include the namespace), it must come before aCheckSet
with a scope matching just that namespace. This property is enforced by server-side validation. The purpose of this restriction is to ensure that if more than oneCheckSet
matches a given Pod, theCheckSet
that will be evaluated will always be the first in the list to match (because if any other matches, it must be less specific). Ifcheck_sets
is empty, the default behavior is to allow all images. Ifcheck_sets
is non-empty, the lastcheck_sets
entry must always be aCheckSet
with no scope set, i.e. a catchall to handle any situation not caught by the precedingCheckSet
objects. - image_
allowlist ImageAllowlist Response - Optional. Images exempted from this policy. If any of the patterns match the image being evaluated, the rest of the policy will not be evaluated.
- check
Sets List<Property Map> - Optional. The
CheckSet
objects to apply, scoped by namespace or namespace and service account. Exactly oneCheckSet
will be evaluated for a given Pod (unless the list is empty, in which case the behavior is "always allow"). If multipleCheckSet
objects have scopes that match the namespace and service account of the Pod being evaluated, only theCheckSet
with the MOST SPECIFIC scope will match.CheckSet
objects must be listed in order of decreasing specificity, i.e. if a scope matches a given service account (which must include the namespace), it must come before aCheckSet
with a scope matching just that namespace. This property is enforced by server-side validation. The purpose of this restriction is to ensure that if more than oneCheckSet
matches a given Pod, theCheckSet
that will be evaluated will always be the first in the list to match (because if any other matches, it must be less specific). Ifcheck_sets
is empty, the default behavior is to allow all images. Ifcheck_sets
is non-empty, the lastcheck_sets
entry must always be aCheckSet
with no scope set, i.e. a catchall to handle any situation not caught by the precedingCheckSet
objects. - image
Allowlist Property Map - Optional. Images exempted from this policy. If any of the patterns match the image being evaluated, the rest of the policy will not be evaluated.
ImageAllowlistResponse
- Allow
Pattern List<string> - A disjunction of image patterns to allow. If any of these patterns match, then the image is considered exempted by this allowlist.
- Allow
Pattern []string - A disjunction of image patterns to allow. If any of these patterns match, then the image is considered exempted by this allowlist.
- allow
Pattern List<String> - A disjunction of image patterns to allow. If any of these patterns match, then the image is considered exempted by this allowlist.
- allow
Pattern string[] - A disjunction of image patterns to allow. If any of these patterns match, then the image is considered exempted by this allowlist.
- allow_
pattern Sequence[str] - A disjunction of image patterns to allow. If any of these patterns match, then the image is considered exempted by this allowlist.
- allow
Pattern List<String> - A disjunction of image patterns to allow. If any of these patterns match, then the image is considered exempted by this allowlist.
ImageFreshnessCheckResponse
- Max
Upload intAge Days - The max number of days that is allowed since the image was uploaded. Must be greater than zero.
- Max
Upload intAge Days - The max number of days that is allowed since the image was uploaded. Must be greater than zero.
- max
Upload IntegerAge Days - The max number of days that is allowed since the image was uploaded. Must be greater than zero.
- max
Upload numberAge Days - The max number of days that is allowed since the image was uploaded. Must be greater than zero.
- max_
upload_ intage_ days - The max number of days that is allowed since the image was uploaded. Must be greater than zero.
- max
Upload NumberAge Days - The max number of days that is allowed since the image was uploaded. Must be greater than zero.
PkixPublicKeyResponse
- Key
Id string - Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them, and that ID must match the contents of this field exactly. This may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If
key_id
is left blank and thisPkixPublicKey
is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If thisPkixPublicKey
is used in the context of a wrapper that has its own notion of key ID (e.g.AttestorPublicKey
), then this field can either: * Match that value exactly. * Or be left blank, in which case it behaves exactly as though it is equal to that wrapper value. - Public
Key stringPem - A PEM-encoded public key, as described in https://tools.ietf.org/html/rfc7468#section-13
- Signature
Algorithm string - The signature algorithm used to verify a message against a signature using this key. These signature algorithm must match the structure and any object identifiers encoded in
public_key_pem
(i.e. this algorithm must match that of the public key).
- Key
Id string - Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them, and that ID must match the contents of this field exactly. This may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If
key_id
is left blank and thisPkixPublicKey
is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If thisPkixPublicKey
is used in the context of a wrapper that has its own notion of key ID (e.g.AttestorPublicKey
), then this field can either: * Match that value exactly. * Or be left blank, in which case it behaves exactly as though it is equal to that wrapper value. - Public
Key stringPem - A PEM-encoded public key, as described in https://tools.ietf.org/html/rfc7468#section-13
- Signature
Algorithm string - The signature algorithm used to verify a message against a signature using this key. These signature algorithm must match the structure and any object identifiers encoded in
public_key_pem
(i.e. this algorithm must match that of the public key).
- key
Id String - Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them, and that ID must match the contents of this field exactly. This may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If
key_id
is left blank and thisPkixPublicKey
is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If thisPkixPublicKey
is used in the context of a wrapper that has its own notion of key ID (e.g.AttestorPublicKey
), then this field can either: * Match that value exactly. * Or be left blank, in which case it behaves exactly as though it is equal to that wrapper value. - public
Key StringPem - A PEM-encoded public key, as described in https://tools.ietf.org/html/rfc7468#section-13
- signature
Algorithm String - The signature algorithm used to verify a message against a signature using this key. These signature algorithm must match the structure and any object identifiers encoded in
public_key_pem
(i.e. this algorithm must match that of the public key).
- key
Id string - Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them, and that ID must match the contents of this field exactly. This may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If
key_id
is left blank and thisPkixPublicKey
is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If thisPkixPublicKey
is used in the context of a wrapper that has its own notion of key ID (e.g.AttestorPublicKey
), then this field can either: * Match that value exactly. * Or be left blank, in which case it behaves exactly as though it is equal to that wrapper value. - public
Key stringPem - A PEM-encoded public key, as described in https://tools.ietf.org/html/rfc7468#section-13
- signature
Algorithm string - The signature algorithm used to verify a message against a signature using this key. These signature algorithm must match the structure and any object identifiers encoded in
public_key_pem
(i.e. this algorithm must match that of the public key).
- key_
id str - Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them, and that ID must match the contents of this field exactly. This may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If
key_id
is left blank and thisPkixPublicKey
is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If thisPkixPublicKey
is used in the context of a wrapper that has its own notion of key ID (e.g.AttestorPublicKey
), then this field can either: * Match that value exactly. * Or be left blank, in which case it behaves exactly as though it is equal to that wrapper value. - public_
key_ strpem - A PEM-encoded public key, as described in https://tools.ietf.org/html/rfc7468#section-13
- signature_
algorithm str - The signature algorithm used to verify a message against a signature using this key. These signature algorithm must match the structure and any object identifiers encoded in
public_key_pem
(i.e. this algorithm must match that of the public key).
- key
Id String - Optional. The ID of this public key. Signatures verified by Binary Authorization must include the ID of the public key that can be used to verify them, and that ID must match the contents of this field exactly. This may be explicitly provided by the caller, but it MUST be a valid RFC3986 URI. If
key_id
is left blank and thisPkixPublicKey
is not used in the context of a wrapper (see next paragraph), a default key ID will be computed based on the digest of the DER encoding of the public key. If thisPkixPublicKey
is used in the context of a wrapper that has its own notion of key ID (e.g.AttestorPublicKey
), then this field can either: * Match that value exactly. * Or be left blank, in which case it behaves exactly as though it is equal to that wrapper value. - public
Key StringPem - A PEM-encoded public key, as described in https://tools.ietf.org/html/rfc7468#section-13
- signature
Algorithm String - The signature algorithm used to verify a message against a signature using this key. These signature algorithm must match the structure and any object identifiers encoded in
public_key_pem
(i.e. this algorithm must match that of the public key).
PkixPublicKeySetResponse
- Pkix
Public List<Pulumi.Keys Google Native. Binary Authorization. V1. Inputs. Pkix Public Key Response> pkix_public_keys
must have at least one entry.
- Pkix
Public []PkixKeys Public Key Response pkix_public_keys
must have at least one entry.
- pkix
Public List<PkixKeys Public Key Response> pkix_public_keys
must have at least one entry.
- pkix
Public PkixKeys Public Key Response[] pkix_public_keys
must have at least one entry.
- pkix_
public_ Sequence[Pkixkeys Public Key Response] pkix_public_keys
must have at least one entry.
- pkix
Public List<Property Map>Keys pkix_public_keys
must have at least one entry.
ScopeResponse
- Kubernetes
Namespace string - Optional. Matches all Kubernetes service accounts in the provided namespace, unless a more specific
kubernetes_service_account
scope already matched. - Kubernetes
Service stringAccount - Optional. Matches a single Kubernetes service account, e.g.
my-namespace:my-service-account
.kubernetes_service_account
scope is always more specific thankubernetes_namespace
scope for the same namespace.
- Kubernetes
Namespace string - Optional. Matches all Kubernetes service accounts in the provided namespace, unless a more specific
kubernetes_service_account
scope already matched. - Kubernetes
Service stringAccount - Optional. Matches a single Kubernetes service account, e.g.
my-namespace:my-service-account
.kubernetes_service_account
scope is always more specific thankubernetes_namespace
scope for the same namespace.
- kubernetes
Namespace String - Optional. Matches all Kubernetes service accounts in the provided namespace, unless a more specific
kubernetes_service_account
scope already matched. - kubernetes
Service StringAccount - Optional. Matches a single Kubernetes service account, e.g.
my-namespace:my-service-account
.kubernetes_service_account
scope is always more specific thankubernetes_namespace
scope for the same namespace.
- kubernetes
Namespace string - Optional. Matches all Kubernetes service accounts in the provided namespace, unless a more specific
kubernetes_service_account
scope already matched. - kubernetes
Service stringAccount - Optional. Matches a single Kubernetes service account, e.g.
my-namespace:my-service-account
.kubernetes_service_account
scope is always more specific thankubernetes_namespace
scope for the same namespace.
- kubernetes_
namespace str - Optional. Matches all Kubernetes service accounts in the provided namespace, unless a more specific
kubernetes_service_account
scope already matched. - kubernetes_
service_ straccount - Optional. Matches a single Kubernetes service account, e.g.
my-namespace:my-service-account
.kubernetes_service_account
scope is always more specific thankubernetes_namespace
scope for the same namespace.
- kubernetes
Namespace String - Optional. Matches all Kubernetes service accounts in the provided namespace, unless a more specific
kubernetes_service_account
scope already matched. - kubernetes
Service StringAccount - Optional. Matches a single Kubernetes service account, e.g.
my-namespace:my-service-account
.kubernetes_service_account
scope is always more specific thankubernetes_namespace
scope for the same namespace.
SimpleSigningAttestationCheckResponse
- Attestation
Authenticators List<Pulumi.Google Native. Binary Authorization. V1. Inputs. Attestation Authenticator Response> - The authenticators required by this check to verify an attestation. Typically this is one or more PKIX public keys for signature verification. Only one authenticator needs to consider an attestation verified in order for an attestation to be considered fully authenticated. In otherwords, this list of authenticators is an "OR" of the authenticator results. At least one authenticator is required.
- Container
Analysis List<string>Attestation Projects - Optional. The projects where attestations are stored as Container Analysis Occurrences. Only one attestation needs to successfully verify an image for this check to pass, so a single verified attestation found in any of
container_analysis_attestation_projects
is sufficient for the check to pass. When fetching Occurrences from Container Analysis, only 'AttestationOccurrence' kinds are considered. In the future, additional Occurrence kinds may be added to the query.
- Attestation
Authenticators []AttestationAuthenticator Response - The authenticators required by this check to verify an attestation. Typically this is one or more PKIX public keys for signature verification. Only one authenticator needs to consider an attestation verified in order for an attestation to be considered fully authenticated. In otherwords, this list of authenticators is an "OR" of the authenticator results. At least one authenticator is required.
- Container
Analysis []stringAttestation Projects - Optional. The projects where attestations are stored as Container Analysis Occurrences. Only one attestation needs to successfully verify an image for this check to pass, so a single verified attestation found in any of
container_analysis_attestation_projects
is sufficient for the check to pass. When fetching Occurrences from Container Analysis, only 'AttestationOccurrence' kinds are considered. In the future, additional Occurrence kinds may be added to the query.
- attestation
Authenticators List<AttestationAuthenticator Response> - The authenticators required by this check to verify an attestation. Typically this is one or more PKIX public keys for signature verification. Only one authenticator needs to consider an attestation verified in order for an attestation to be considered fully authenticated. In otherwords, this list of authenticators is an "OR" of the authenticator results. At least one authenticator is required.
- container
Analysis List<String>Attestation Projects - Optional. The projects where attestations are stored as Container Analysis Occurrences. Only one attestation needs to successfully verify an image for this check to pass, so a single verified attestation found in any of
container_analysis_attestation_projects
is sufficient for the check to pass. When fetching Occurrences from Container Analysis, only 'AttestationOccurrence' kinds are considered. In the future, additional Occurrence kinds may be added to the query.
- attestation
Authenticators AttestationAuthenticator Response[] - The authenticators required by this check to verify an attestation. Typically this is one or more PKIX public keys for signature verification. Only one authenticator needs to consider an attestation verified in order for an attestation to be considered fully authenticated. In otherwords, this list of authenticators is an "OR" of the authenticator results. At least one authenticator is required.
- container
Analysis string[]Attestation Projects - Optional. The projects where attestations are stored as Container Analysis Occurrences. Only one attestation needs to successfully verify an image for this check to pass, so a single verified attestation found in any of
container_analysis_attestation_projects
is sufficient for the check to pass. When fetching Occurrences from Container Analysis, only 'AttestationOccurrence' kinds are considered. In the future, additional Occurrence kinds may be added to the query.
- attestation_
authenticators Sequence[AttestationAuthenticator Response] - The authenticators required by this check to verify an attestation. Typically this is one or more PKIX public keys for signature verification. Only one authenticator needs to consider an attestation verified in order for an attestation to be considered fully authenticated. In otherwords, this list of authenticators is an "OR" of the authenticator results. At least one authenticator is required.
- container_
analysis_ Sequence[str]attestation_ projects - Optional. The projects where attestations are stored as Container Analysis Occurrences. Only one attestation needs to successfully verify an image for this check to pass, so a single verified attestation found in any of
container_analysis_attestation_projects
is sufficient for the check to pass. When fetching Occurrences from Container Analysis, only 'AttestationOccurrence' kinds are considered. In the future, additional Occurrence kinds may be added to the query.
- attestation
Authenticators List<Property Map> - The authenticators required by this check to verify an attestation. Typically this is one or more PKIX public keys for signature verification. Only one authenticator needs to consider an attestation verified in order for an attestation to be considered fully authenticated. In otherwords, this list of authenticators is an "OR" of the authenticator results. At least one authenticator is required.
- container
Analysis List<String>Attestation Projects - Optional. The projects where attestations are stored as Container Analysis Occurrences. Only one attestation needs to successfully verify an image for this check to pass, so a single verified attestation found in any of
container_analysis_attestation_projects
is sufficient for the check to pass. When fetching Occurrences from Container Analysis, only 'AttestationOccurrence' kinds are considered. In the future, additional Occurrence kinds may be added to the query.
SlsaCheckResponse
- Rules
List<Pulumi.
Google Native. Binary Authorization. V1. Inputs. Verification Rule Response> - Specifies a list of verification rules for the SLSA attestations. An image is considered compliant with the SlsaCheck if any of the rules are satisfied.
- Rules
[]Verification
Rule Response - Specifies a list of verification rules for the SLSA attestations. An image is considered compliant with the SlsaCheck if any of the rules are satisfied.
- rules
List<Verification
Rule Response> - Specifies a list of verification rules for the SLSA attestations. An image is considered compliant with the SlsaCheck if any of the rules are satisfied.
- rules
Verification
Rule Response[] - Specifies a list of verification rules for the SLSA attestations. An image is considered compliant with the SlsaCheck if any of the rules are satisfied.
- rules
Sequence[Verification
Rule Response] - Specifies a list of verification rules for the SLSA attestations. An image is considered compliant with the SlsaCheck if any of the rules are satisfied.
- rules List<Property Map>
- Specifies a list of verification rules for the SLSA attestations. An image is considered compliant with the SlsaCheck if any of the rules are satisfied.
TrustedDirectoryCheckResponse
- Trusted
Dir List<string>Patterns - List of trusted directory patterns. A pattern is in the form "registry/path/to/directory". The registry domain part is defined as two or more dot-separated words, e.g.,
us.pkg.dev
, orgcr.io
. Additionally,*
can be used in three ways as wildcards: 1. leading*
to match varying prefixes in registry subdomain (useful for location prefixes); 2. trailing*
after registry/ to match varying endings; 3. trailing**
after registry/ to match "/" as well. For example: --gcr.io/my-project/my-repo
is valid to match a single directory --*-docker.pkg.dev/my-project/my-repo
or*.gcr.io/my-project
are valid to match varying prefixes --gcr.io/my-project/*
will match all direct directories inmy-project
--gcr.io/my-project/**
would match all directories inmy-project
--gcr.i*
is not allowed since the registry is not completely specified --sub*domain.gcr.io/nginx
is not valid because only leading*
or trailing*
are allowed. --*pkg.dev/my-project/my-repo
is not valid because leading*
can only match subdomain --**-docker.pkg.dev
is not valid because one leading*
is allowed, and that it cannot match/
- Trusted
Dir []stringPatterns - List of trusted directory patterns. A pattern is in the form "registry/path/to/directory". The registry domain part is defined as two or more dot-separated words, e.g.,
us.pkg.dev
, orgcr.io
. Additionally,*
can be used in three ways as wildcards: 1. leading*
to match varying prefixes in registry subdomain (useful for location prefixes); 2. trailing*
after registry/ to match varying endings; 3. trailing**
after registry/ to match "/" as well. For example: --gcr.io/my-project/my-repo
is valid to match a single directory --*-docker.pkg.dev/my-project/my-repo
or*.gcr.io/my-project
are valid to match varying prefixes --gcr.io/my-project/*
will match all direct directories inmy-project
--gcr.io/my-project/**
would match all directories inmy-project
--gcr.i*
is not allowed since the registry is not completely specified --sub*domain.gcr.io/nginx
is not valid because only leading*
or trailing*
are allowed. --*pkg.dev/my-project/my-repo
is not valid because leading*
can only match subdomain --**-docker.pkg.dev
is not valid because one leading*
is allowed, and that it cannot match/
- trusted
Dir List<String>Patterns - List of trusted directory patterns. A pattern is in the form "registry/path/to/directory". The registry domain part is defined as two or more dot-separated words, e.g.,
us.pkg.dev
, orgcr.io
. Additionally,*
can be used in three ways as wildcards: 1. leading*
to match varying prefixes in registry subdomain (useful for location prefixes); 2. trailing*
after registry/ to match varying endings; 3. trailing**
after registry/ to match "/" as well. For example: --gcr.io/my-project/my-repo
is valid to match a single directory --*-docker.pkg.dev/my-project/my-repo
or*.gcr.io/my-project
are valid to match varying prefixes --gcr.io/my-project/*
will match all direct directories inmy-project
--gcr.io/my-project/**
would match all directories inmy-project
--gcr.i*
is not allowed since the registry is not completely specified --sub*domain.gcr.io/nginx
is not valid because only leading*
or trailing*
are allowed. --*pkg.dev/my-project/my-repo
is not valid because leading*
can only match subdomain --**-docker.pkg.dev
is not valid because one leading*
is allowed, and that it cannot match/
- trusted
Dir string[]Patterns - List of trusted directory patterns. A pattern is in the form "registry/path/to/directory". The registry domain part is defined as two or more dot-separated words, e.g.,
us.pkg.dev
, orgcr.io
. Additionally,*
can be used in three ways as wildcards: 1. leading*
to match varying prefixes in registry subdomain (useful for location prefixes); 2. trailing*
after registry/ to match varying endings; 3. trailing**
after registry/ to match "/" as well. For example: --gcr.io/my-project/my-repo
is valid to match a single directory --*-docker.pkg.dev/my-project/my-repo
or*.gcr.io/my-project
are valid to match varying prefixes --gcr.io/my-project/*
will match all direct directories inmy-project
--gcr.io/my-project/**
would match all directories inmy-project
--gcr.i*
is not allowed since the registry is not completely specified --sub*domain.gcr.io/nginx
is not valid because only leading*
or trailing*
are allowed. --*pkg.dev/my-project/my-repo
is not valid because leading*
can only match subdomain --**-docker.pkg.dev
is not valid because one leading*
is allowed, and that it cannot match/
- trusted_
dir_ Sequence[str]patterns - List of trusted directory patterns. A pattern is in the form "registry/path/to/directory". The registry domain part is defined as two or more dot-separated words, e.g.,
us.pkg.dev
, orgcr.io
. Additionally,*
can be used in three ways as wildcards: 1. leading*
to match varying prefixes in registry subdomain (useful for location prefixes); 2. trailing*
after registry/ to match varying endings; 3. trailing**
after registry/ to match "/" as well. For example: --gcr.io/my-project/my-repo
is valid to match a single directory --*-docker.pkg.dev/my-project/my-repo
or*.gcr.io/my-project
are valid to match varying prefixes --gcr.io/my-project/*
will match all direct directories inmy-project
--gcr.io/my-project/**
would match all directories inmy-project
--gcr.i*
is not allowed since the registry is not completely specified --sub*domain.gcr.io/nginx
is not valid because only leading*
or trailing*
are allowed. --*pkg.dev/my-project/my-repo
is not valid because leading*
can only match subdomain --**-docker.pkg.dev
is not valid because one leading*
is allowed, and that it cannot match/
- trusted
Dir List<String>Patterns - List of trusted directory patterns. A pattern is in the form "registry/path/to/directory". The registry domain part is defined as two or more dot-separated words, e.g.,
us.pkg.dev
, orgcr.io
. Additionally,*
can be used in three ways as wildcards: 1. leading*
to match varying prefixes in registry subdomain (useful for location prefixes); 2. trailing*
after registry/ to match varying endings; 3. trailing**
after registry/ to match "/" as well. For example: --gcr.io/my-project/my-repo
is valid to match a single directory --*-docker.pkg.dev/my-project/my-repo
or*.gcr.io/my-project
are valid to match varying prefixes --gcr.io/my-project/*
will match all direct directories inmy-project
--gcr.io/my-project/**
would match all directories inmy-project
--gcr.i*
is not allowed since the registry is not completely specified --sub*domain.gcr.io/nginx
is not valid because only leading*
or trailing*
are allowed. --*pkg.dev/my-project/my-repo
is not valid because leading*
can only match subdomain --**-docker.pkg.dev
is not valid because one leading*
is allowed, and that it cannot match/
VerificationRuleResponse
- Attestation
Source Pulumi.Google Native. Binary Authorization. V1. Inputs. Attestation Source Response - Specifies where to fetch the provenances attestations generated by the builder (group).
- Config
Based boolBuild Required - If true, require the image to be built from a top-level configuration.
trusted_source_repo_patterns
specifies the repositories containing this configuration. - Trusted
Builder string - Each verification rule is used for evaluation against provenances generated by a specific builder (group). For some of the builders, such as the Google Cloud Build, users don't need to explicitly specify their roots of trust in the policy since the evaluation service can automatically fetch them based on the builder (group).
- Trusted
Source List<string>Repo Patterns - List of trusted source code repository URL patterns. These patterns match the full repository URL without its scheme (e.g.
https://
). The patterns must not include schemes. For example, the patternsource.cloud.google.com/my-project/my-repo-name
matches the following URLs: -source.cloud.google.com/my-project/my-repo-name
-git+ssh://source.cloud.google.com/my-project/my-repo-name
-https://source.cloud.google.com/my-project/my-repo-name
A pattern matches a URL either exactly or with*
wildcards.*
can be used in only two ways: 1. trailing*
after hosturi/ to match varying endings; 2. trailing**
after hosturi/ to match/
as well.*
and**
can only be used as wildcards and can only occur at the end of the pattern after a/
. (So it's not possible to match a URL that contains literal*
.) For example: -github.com/my-project/my-repo
is valid to match a single repo -github.com/my-project/*
will match all direct repos inmy-project
-github.com/**
matches all repos in GitHub
- Attestation
Source AttestationSource Response - Specifies where to fetch the provenances attestations generated by the builder (group).
- Config
Based boolBuild Required - If true, require the image to be built from a top-level configuration.
trusted_source_repo_patterns
specifies the repositories containing this configuration. - Trusted
Builder string - Each verification rule is used for evaluation against provenances generated by a specific builder (group). For some of the builders, such as the Google Cloud Build, users don't need to explicitly specify their roots of trust in the policy since the evaluation service can automatically fetch them based on the builder (group).
- Trusted
Source []stringRepo Patterns - List of trusted source code repository URL patterns. These patterns match the full repository URL without its scheme (e.g.
https://
). The patterns must not include schemes. For example, the patternsource.cloud.google.com/my-project/my-repo-name
matches the following URLs: -source.cloud.google.com/my-project/my-repo-name
-git+ssh://source.cloud.google.com/my-project/my-repo-name
-https://source.cloud.google.com/my-project/my-repo-name
A pattern matches a URL either exactly or with*
wildcards.*
can be used in only two ways: 1. trailing*
after hosturi/ to match varying endings; 2. trailing**
after hosturi/ to match/
as well.*
and**
can only be used as wildcards and can only occur at the end of the pattern after a/
. (So it's not possible to match a URL that contains literal*
.) For example: -github.com/my-project/my-repo
is valid to match a single repo -github.com/my-project/*
will match all direct repos inmy-project
-github.com/**
matches all repos in GitHub
- attestation
Source AttestationSource Response - Specifies where to fetch the provenances attestations generated by the builder (group).
- config
Based BooleanBuild Required - If true, require the image to be built from a top-level configuration.
trusted_source_repo_patterns
specifies the repositories containing this configuration. - trusted
Builder String - Each verification rule is used for evaluation against provenances generated by a specific builder (group). For some of the builders, such as the Google Cloud Build, users don't need to explicitly specify their roots of trust in the policy since the evaluation service can automatically fetch them based on the builder (group).
- trusted
Source List<String>Repo Patterns - List of trusted source code repository URL patterns. These patterns match the full repository URL without its scheme (e.g.
https://
). The patterns must not include schemes. For example, the patternsource.cloud.google.com/my-project/my-repo-name
matches the following URLs: -source.cloud.google.com/my-project/my-repo-name
-git+ssh://source.cloud.google.com/my-project/my-repo-name
-https://source.cloud.google.com/my-project/my-repo-name
A pattern matches a URL either exactly or with*
wildcards.*
can be used in only two ways: 1. trailing*
after hosturi/ to match varying endings; 2. trailing**
after hosturi/ to match/
as well.*
and**
can only be used as wildcards and can only occur at the end of the pattern after a/
. (So it's not possible to match a URL that contains literal*
.) For example: -github.com/my-project/my-repo
is valid to match a single repo -github.com/my-project/*
will match all direct repos inmy-project
-github.com/**
matches all repos in GitHub
- attestation
Source AttestationSource Response - Specifies where to fetch the provenances attestations generated by the builder (group).
- config
Based booleanBuild Required - If true, require the image to be built from a top-level configuration.
trusted_source_repo_patterns
specifies the repositories containing this configuration. - trusted
Builder string - Each verification rule is used for evaluation against provenances generated by a specific builder (group). For some of the builders, such as the Google Cloud Build, users don't need to explicitly specify their roots of trust in the policy since the evaluation service can automatically fetch them based on the builder (group).
- trusted
Source string[]Repo Patterns - List of trusted source code repository URL patterns. These patterns match the full repository URL without its scheme (e.g.
https://
). The patterns must not include schemes. For example, the patternsource.cloud.google.com/my-project/my-repo-name
matches the following URLs: -source.cloud.google.com/my-project/my-repo-name
-git+ssh://source.cloud.google.com/my-project/my-repo-name
-https://source.cloud.google.com/my-project/my-repo-name
A pattern matches a URL either exactly or with*
wildcards.*
can be used in only two ways: 1. trailing*
after hosturi/ to match varying endings; 2. trailing**
after hosturi/ to match/
as well.*
and**
can only be used as wildcards and can only occur at the end of the pattern after a/
. (So it's not possible to match a URL that contains literal*
.) For example: -github.com/my-project/my-repo
is valid to match a single repo -github.com/my-project/*
will match all direct repos inmy-project
-github.com/**
matches all repos in GitHub
- attestation_
source AttestationSource Response - Specifies where to fetch the provenances attestations generated by the builder (group).
- config_
based_ boolbuild_ required - If true, require the image to be built from a top-level configuration.
trusted_source_repo_patterns
specifies the repositories containing this configuration. - trusted_
builder str - Each verification rule is used for evaluation against provenances generated by a specific builder (group). For some of the builders, such as the Google Cloud Build, users don't need to explicitly specify their roots of trust in the policy since the evaluation service can automatically fetch them based on the builder (group).
- trusted_
source_ Sequence[str]repo_ patterns - List of trusted source code repository URL patterns. These patterns match the full repository URL without its scheme (e.g.
https://
). The patterns must not include schemes. For example, the patternsource.cloud.google.com/my-project/my-repo-name
matches the following URLs: -source.cloud.google.com/my-project/my-repo-name
-git+ssh://source.cloud.google.com/my-project/my-repo-name
-https://source.cloud.google.com/my-project/my-repo-name
A pattern matches a URL either exactly or with*
wildcards.*
can be used in only two ways: 1. trailing*
after hosturi/ to match varying endings; 2. trailing**
after hosturi/ to match/
as well.*
and**
can only be used as wildcards and can only occur at the end of the pattern after a/
. (So it's not possible to match a URL that contains literal*
.) For example: -github.com/my-project/my-repo
is valid to match a single repo -github.com/my-project/*
will match all direct repos inmy-project
-github.com/**
matches all repos in GitHub
- attestation
Source Property Map - Specifies where to fetch the provenances attestations generated by the builder (group).
- config
Based BooleanBuild Required - If true, require the image to be built from a top-level configuration.
trusted_source_repo_patterns
specifies the repositories containing this configuration. - trusted
Builder String - Each verification rule is used for evaluation against provenances generated by a specific builder (group). For some of the builders, such as the Google Cloud Build, users don't need to explicitly specify their roots of trust in the policy since the evaluation service can automatically fetch them based on the builder (group).
- trusted
Source List<String>Repo Patterns - List of trusted source code repository URL patterns. These patterns match the full repository URL without its scheme (e.g.
https://
). The patterns must not include schemes. For example, the patternsource.cloud.google.com/my-project/my-repo-name
matches the following URLs: -source.cloud.google.com/my-project/my-repo-name
-git+ssh://source.cloud.google.com/my-project/my-repo-name
-https://source.cloud.google.com/my-project/my-repo-name
A pattern matches a URL either exactly or with*
wildcards.*
can be used in only two ways: 1. trailing*
after hosturi/ to match varying endings; 2. trailing**
after hosturi/ to match/
as well.*
and**
can only be used as wildcards and can only occur at the end of the pattern after a/
. (So it's not possible to match a URL that contains literal*
.) For example: -github.com/my-project/my-repo
is valid to match a single repo -github.com/my-project/*
will match all direct repos inmy-project
-github.com/**
matches all repos in GitHub
VulnerabilityCheckResponse
- Allowed
Cves List<string> - Optional. A list of specific CVEs to ignore even if the vulnerability level violates
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will allow vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - Blocked
Cves List<string> - Optional. A list of specific CVEs to always raise warnings about even if the vulnerability level meets
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will block vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - Container
Analysis List<string>Vulnerability Projects - Optional. The projects where vulnerabilities are stored as Container Analysis Occurrences. Each project is expressed in the resource format of
projects/[PROJECT_ID]
, e.g.,projects/my-gcp-project
. An attempt will be made for each project to fetch vulnerabilities, and all valid vulnerabilities will be used to check against the vulnerability policy. If no valid scan is found in all projects configured here, an error will be returned for the check. - Maximum
Fixable stringSeverity - The threshold for severity for which a fix is currently available. This field is required and must be set.
- Maximum
Unfixable stringSeverity - The threshold for severity for which a fix isn't currently available. This field is required and must be set.
- Allowed
Cves []string - Optional. A list of specific CVEs to ignore even if the vulnerability level violates
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will allow vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - Blocked
Cves []string - Optional. A list of specific CVEs to always raise warnings about even if the vulnerability level meets
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will block vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - Container
Analysis []stringVulnerability Projects - Optional. The projects where vulnerabilities are stored as Container Analysis Occurrences. Each project is expressed in the resource format of
projects/[PROJECT_ID]
, e.g.,projects/my-gcp-project
. An attempt will be made for each project to fetch vulnerabilities, and all valid vulnerabilities will be used to check against the vulnerability policy. If no valid scan is found in all projects configured here, an error will be returned for the check. - Maximum
Fixable stringSeverity - The threshold for severity for which a fix is currently available. This field is required and must be set.
- Maximum
Unfixable stringSeverity - The threshold for severity for which a fix isn't currently available. This field is required and must be set.
- allowed
Cves List<String> - Optional. A list of specific CVEs to ignore even if the vulnerability level violates
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will allow vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - blocked
Cves List<String> - Optional. A list of specific CVEs to always raise warnings about even if the vulnerability level meets
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will block vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - container
Analysis List<String>Vulnerability Projects - Optional. The projects where vulnerabilities are stored as Container Analysis Occurrences. Each project is expressed in the resource format of
projects/[PROJECT_ID]
, e.g.,projects/my-gcp-project
. An attempt will be made for each project to fetch vulnerabilities, and all valid vulnerabilities will be used to check against the vulnerability policy. If no valid scan is found in all projects configured here, an error will be returned for the check. - maximum
Fixable StringSeverity - The threshold for severity for which a fix is currently available. This field is required and must be set.
- maximum
Unfixable StringSeverity - The threshold for severity for which a fix isn't currently available. This field is required and must be set.
- allowed
Cves string[] - Optional. A list of specific CVEs to ignore even if the vulnerability level violates
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will allow vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - blocked
Cves string[] - Optional. A list of specific CVEs to always raise warnings about even if the vulnerability level meets
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will block vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - container
Analysis string[]Vulnerability Projects - Optional. The projects where vulnerabilities are stored as Container Analysis Occurrences. Each project is expressed in the resource format of
projects/[PROJECT_ID]
, e.g.,projects/my-gcp-project
. An attempt will be made for each project to fetch vulnerabilities, and all valid vulnerabilities will be used to check against the vulnerability policy. If no valid scan is found in all projects configured here, an error will be returned for the check. - maximum
Fixable stringSeverity - The threshold for severity for which a fix is currently available. This field is required and must be set.
- maximum
Unfixable stringSeverity - The threshold for severity for which a fix isn't currently available. This field is required and must be set.
- allowed_
cves Sequence[str] - Optional. A list of specific CVEs to ignore even if the vulnerability level violates
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will allow vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - blocked_
cves Sequence[str] - Optional. A list of specific CVEs to always raise warnings about even if the vulnerability level meets
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will block vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - container_
analysis_ Sequence[str]vulnerability_ projects - Optional. The projects where vulnerabilities are stored as Container Analysis Occurrences. Each project is expressed in the resource format of
projects/[PROJECT_ID]
, e.g.,projects/my-gcp-project
. An attempt will be made for each project to fetch vulnerabilities, and all valid vulnerabilities will be used to check against the vulnerability policy. If no valid scan is found in all projects configured here, an error will be returned for the check. - maximum_
fixable_ strseverity - The threshold for severity for which a fix is currently available. This field is required and must be set.
- maximum_
unfixable_ strseverity - The threshold for severity for which a fix isn't currently available. This field is required and must be set.
- allowed
Cves List<String> - Optional. A list of specific CVEs to ignore even if the vulnerability level violates
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will allow vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - blocked
Cves List<String> - Optional. A list of specific CVEs to always raise warnings about even if the vulnerability level meets
maximumUnfixableSeverity
ormaximumFixableSeverity
. CVEs are listed in the format of Container Analysis note id. For example: - CVE-2021-20305 - CVE-2020-10543 The CVEs are applicable regardless of note provider project, e.g., an entry ofCVE-2021-20305
will block vulnerabilities with a note name of eitherprojects/goog-vulnz/notes/CVE-2021-20305
orprojects/CUSTOM-PROJECT/notes/CVE-2021-20305
. - container
Analysis List<String>Vulnerability Projects - Optional. The projects where vulnerabilities are stored as Container Analysis Occurrences. Each project is expressed in the resource format of
projects/[PROJECT_ID]
, e.g.,projects/my-gcp-project
. An attempt will be made for each project to fetch vulnerabilities, and all valid vulnerabilities will be used to check against the vulnerability policy. If no valid scan is found in all projects configured here, an error will be returned for the check. - maximum
Fixable StringSeverity - The threshold for severity for which a fix is currently available. This field is required and must be set.
- maximum
Unfixable StringSeverity - The threshold for severity for which a fix isn't currently available. This field is required and must be set.
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi