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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hash sums to google_storage_bucket_object_content
#13002
Open
glerchundi opened this issue
Nov 10, 2022
· 0 comments
路 May be fixed by GoogleCloudPlatform/magic-modules#6895
Open
Add hash sums to google_storage_bucket_object_content
#13002
glerchundi opened this issue
Nov 10, 2022
· 0 comments
路 May be fixed by GoogleCloudPlatform/magic-modules#6895
Milestone
Comments
glerchundi
added a commit
to glerchundi/magic-modules
that referenced
this issue
Nov 30, 2022
This returns the same content present in the return object but exposed by using Base64 encoding. This is mostly useful for reading binary content. Our particular use case is to push the content of a WASM file to a Fastly Compute@Edge service. But this is also useful for other serverless services like AWS Lambda as well. This alongside including the hash sums for the source object content proposed in hashicorp/terraform-provider-google#13002, would allow us pushing content directly from Google Storage Object Content data source to Fastly Compute@Edge. AWS Lambda also uses the same version/content discrimination method of sending the content hash sum within the `source_code_hash` parameter. Sign-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
5 tasks
glerchundi
added a commit
to glerchundi/magic-modules
that referenced
this issue
Nov 30, 2022
This returns the same content present in the return object but exposed by using Base64 encoding. This is mostly useful for reading binary content. Our particular use case is to push the content of a WASM file to a Fastly Compute@Edge service. But this is also useful for other serverless services like AWS Lambda as well. This alongside including the hash sums for the source object content proposed in hashicorp/terraform-provider-google#13002, would allow us pushing content directly from Google Storage Object Content data source to Fastly Compute@Edge. AWS Lambda also uses the same version/content discrimination method of sending the content hash sum within the `source_code_hash` parameter. Sign-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
glerchundi
added a commit
to glerchundi/magic-modules
that referenced
this issue
Nov 30, 2022
This returns the same content present in the return object but exposed by using Base64 encoding. This is mostly useful for reading binary content. Our particular use case is to push the content of a WASM file to a Fastly Compute@Edge service. But this is also useful for other serverless services like AWS Lambda as well. This alongside including the hash sums for the source object content proposed in hashicorp/terraform-provider-google#13002, would allow us pushing content directly from Google Storage Object Content data source to Fastly Compute@Edge. AWS Lambda also uses the same version/content discrimination method of sending the content hash sum within the `source_code_hash` parameter. Sign-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
glerchundi
added a commit
to glerchundi/magic-modules
that referenced
this issue
Dec 3, 2022
This returns the same content present in the return object but exposed by using Base64 encoding. This is mostly useful for reading binary content. Our particular use case is to push the content of a WASM file to a Fastly Compute@Edge service. But this is also useful for other serverless services like AWS Lambda as well. This alongside including the hash sums for the source object content proposed in hashicorp/terraform-provider-google#13002, would allow us pushing content directly from Google Storage Object Content data source to Fastly Compute@Edge. AWS Lambda also uses the same version/content discrimination method of sending the content hash sum within the `source_code_hash` parameter. Sign-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
glerchundi
added a commit
to glerchundi/magic-modules
that referenced
this issue
Dec 3, 2022
This returns the same content present in the return object but exposed by using Base64 encoding. This is mostly useful for reading binary content. Our particular use case is to push the content of a WASM file to a Fastly Compute@Edge service. But this is also useful for other serverless services like AWS Lambda as well. This alongside including the hash sums for the source object content proposed in hashicorp/terraform-provider-google#13002, would allow us pushing content directly from Google Storage Object Content data source to Fastly Compute@Edge. AWS Lambda also uses the same version/content discrimination method of sending the content hash sum within the `source_code_hash` parameter. Sign-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
glerchundi
added a commit
to glerchundi/magic-modules
that referenced
this issue
Dec 3, 2022
This returns the same content present in the return object but exposed by using Base64 encoding. This is mostly useful for reading binary content. Our particular use case is to push the content of a WASM file to a Fastly Compute@Edge service. But this is also useful for other serverless services like AWS Lambda as well. This alongside including the hash sums for the source object content proposed in hashicorp/terraform-provider-google#13002, would allow us pushing content directly from Google Storage Object Content data source to Fastly Compute@Edge. AWS Lambda also uses the same version/content discrimination method of sending the content hash sum within the `source_code_hash` parameter. Sign-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
glerchundi
added a commit
to glerchundi/magic-modules
that referenced
this issue
Dec 3, 2022
This returns the same content present in the return object but exposed by using Base64 encoding. This is mostly useful for reading binary content. Our particular use case is to push the content of a WASM file to a Fastly Compute@Edge service. But this is also useful for other serverless services like AWS Lambda as well. This alongside including the hash sums for the source object content proposed in hashicorp/terraform-provider-google#13002, would allow us pushing content directly from Google Storage Object Content data source to Fastly Compute@Edge. AWS Lambda also uses the same version/content discrimination method of sending the content hash sum within the `source_code_hash` parameter. Sign-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Community Note
Description
In order to add
source_code_hash
parameters in some of the providers that accept package contents like AWS Lambda or Fastly Compute@Edge, I propose expose file hash sums to directly pipe into the external provider services.New or Affected Resource(s)
google_storage_bucket_object_content
Potential Terraform Configuration
This is I would like to do:
Other PRs
content_base64
(as shown in the example) to Fastly's Terraform provider: to be created once merged the previous.google_storage_bucket_object_content
: Add support for base64-encoded binary content to google_storage_bucket_object_content datasource聽#10835.References
b/275608337
The text was updated successfully, but these errors were encountered: