1apiVersion: spaces.digitalocean.m.crossplane.io/v1alpha1
2kind: BucketCorsConfiguration
BucketCorsConfigurationSpec defines the desired state of BucketCorsConfiguration
(No description available)
Set of origins and methods (cross-origin access that you want to allow). See below. You can configure up to 100 rules.
Set of Headers that are specified in the Access-Control-Request-Headers header.
Set of HTTP methods that you allow the origin to execute. Valid values are GET, PUT, HEAD, POST, and DELETE.
Set of origins you want customers to be able to access the bucket from.
Set of headers in the response that you want customers to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Set of origins and methods (cross-origin access that you want to allow). See below. You can configure up to 100 rules.
Set of Headers that are specified in the Access-Control-Request-Headers header.
Set of HTTP methods that you allow the origin to execute. Valid values are GET, PUT, HEAD, POST, and DELETE.
Set of origins you want customers to be able to access the bucket from.
Set of headers in the response that you want customers to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
BucketCorsConfigurationStatus defines the observed state of BucketCorsConfiguration.
(No description available)
Set of origins and methods (cross-origin access that you want to allow). See below. You can configure up to 100 rules.
Set of Headers that are specified in the Access-Control-Request-Headers header.
Set of HTTP methods that you allow the origin to execute. Valid values are GET, PUT, HEAD, POST, and DELETE.
Set of origins you want customers to be able to access the bucket from.
Set of headers in the response that you want customers to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).
Conditions of the resource.