-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for storage_hmac_key
resource
#51
Labels
Comments
julienduchesne
added a commit
to grafana/crossplane-provider-gcp
that referenced
this issue
Mar 28, 2023
Issue: crossplane-contrib#51 This resource is needed to do S3-style access on GCS buckets
julienduchesne
added a commit
to grafana/crossplane-provider-gcp
that referenced
this issue
Mar 28, 2023
Issue: crossplane-contrib#51 This resource is needed to do S3-style access on GCS buckets As this comment shows: crossplane-contrib#197 (comment), this resource causes an import cycle However, we can resolve that by putting the resource in the `cloudplatform` package. While, this key is specific to storage, it is still just a product of a service account and isn't linked to any storage resources. Signed-off-by: Julien Duchesne <[email protected]>
1 task
julienduchesne
added a commit
to grafana/crossplane-provider-gcp
that referenced
this issue
Apr 10, 2023
Issue: crossplane-contrib#51 This resource is needed to do S3-style access on GCS buckets As this comment shows: crossplane-contrib#197 (comment), this resource causes an import cycle However, we can resolve that by putting the resource in the `cloudplatform` package. While, this key is specific to storage, it is still just a product of a service account and isn't linked to any storage resources. Signed-off-by: Julien Duchesne <[email protected]>
julienduchesne
added a commit
to grafana/crossplane-provider-gcp
that referenced
this issue
May 2, 2023
Issue: crossplane-contrib#51 This resource is needed to do S3-style access on GCS buckets As this comment shows: crossplane-contrib#197 (comment), this resource causes an import cycle However, we can resolve that by putting the resource in the `cloudplatform` package. While, this key is specific to storage, it is still just a product of a service account and isn't linked to any storage resources. Signed-off-by: Julien Duchesne <[email protected]>
julienduchesne
added a commit
to grafana/crossplane-provider-gcp
that referenced
this issue
Jun 12, 2023
Issue: crossplane-contrib#51 This resource is needed to do S3-style access on GCS buckets As this comment shows: crossplane-contrib#197 (comment), this resource causes an import cycle However, we can resolve that by putting the resource in the `cloudplatform` package. While, this key is specific to storage, it is still just a product of a service account and isn't linked to any storage resources. Signed-off-by: Julien Duchesne <[email protected]>
This is very much needed on our case. Hope it will be merged soon. |
We're looking forward to this merge as it's essential for our Infrastructure as Code strategy to take off. Hoping it happens shortly! 🙏 🙏 |
We also need this feature for library not compatible with GCS (Uppy > S3 Only) |
I've sent an implementation of storage_hmac_key in #546. Hopefully we can get it in as we also depend on it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What resource do you need?
Terraform Resource Name: storage_hmac_key
What is your use case?
Lack of storage_hmac_key prevents any client usage of GCS buckets as AWS S3 buckets.
storage_hmac_key is required for GCS bucket to be used by clients through the AWS S3 API instead of GCS API.
See the following related documentation:
https://cloud.google.com/storage/docs/aws-simple-migration
https://cloud.google.com/storage/docs/authentication/hmackeys
https://cloud.google.com/storage/docs/authentication/managing-hmackeys#terraform
This resource was present in https://doc.crds.dev/github.com/crossplane-contrib/provider-jet-gcp/storage.gcp.jet.crossplane.io/HMACKey/[email protected]
/CC
The text was updated successfully, but these errors were encountered: