provider-gcp icon indicating copy to clipboard operation
provider-gcp copied to clipboard

Crossplane GCP provider

Results 105 provider-gcp issues
Sort by recently updated
recently updated
newest added

### What happened? I've created a GCP Storage Bucket with this provider. When I tried to add a lifecycle rule that should delete objects older than 0 days, provider reports...

bug

### What problem are you facing? I am trying to set a Maintenance Policy for Memorystore Redis instances, but everything I try is unsuccessful. This instance gets created but doesnt...

enhancement

### Description of your changes In order to send the correct signal to the community about the maintainers of this provider, I updated the `OWNERS.md` file. I have shifted my...

### Description of your changes Fixes #498 I have: - [x] Read and followed Crossplane's [contribution process]. - [x] Run `make reviewable test` to ensure this PR is ready for...

### What problem are you facing? Current implementation of provider-gcp is not supporting ability to enable TLS for MemoryStore redis provisioning requests. On GCP side enabling of TLS triggers creation...

enhancement

Hello, any plans to add Private Service Connect crds to this provider?

enhancement

### What happened? The GCP Provider fails to install. I am running crossplane on a private GKE cluster (company standards) so the nodes do not have public IP addresses and...

bug

### What problem are you facing? With https://github.com/crossplane/crossplane-runtime/pull/372, we have introduced a DesiredStateChanged to the xp runtime, which would filter out status update events. We need to add this as...

enhancement
good first issue

### Description of your changes This PR adds a flag for Management Policies (a.k.a.) [Observe Only resources](https://github.com/crossplane/crossplane/blob/master/design/design-doc-observe-only-resources.md#observe-only-resources). Please note, this PR does not cover representing the full state at status.atProvider...

### What problem are you facing? With the recent design for Observe Only resource, we expect to have the full state under `status.atProvider`, i.e. `status.atProvider` should be superset of `spec.forProvider`....

enhancement