Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clean up markdown for signed_url a bit #2457

Merged
merged 2 commits into from
Oct 10, 2019
Merged

Clean up markdown for signed_url a bit #2457

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1d0566c
Clean up markdown for signed_url a bit
gmile Oct 10, 2019
cb9c57e
Update tracked submodules -> HEAD on Thu Oct 10 17:11:15 UTC 2019
modular-magician Oct 10, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions third_party/terraform/website/docs/d/signed_url.html.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,10 @@ For more info about signed URL's is available [here](https://cloud.google.com/st
data "google_storage_object_signed_url" "artifact" {
bucket = "install_binaries"
path = "path/to/install_file.bin"

}

resource "google_compute_instance" "vm" {
name = "vm"
...

provisioner "remote-exec" {
inline = [
Expand Down Expand Up @@ -64,7 +62,7 @@ The following arguments are supported:
* `credentials` - (Optional) What Google service account credentials json should be used to sign the URL.
This data source checks the following locations for credentials, in order of preference: data source `credentials` attribute, provider `credentials` attribute and finally the GOOGLE_APPLICATION_CREDENTIALS environment variable.

> **NOTE** the default google credentials configured by `gcloud` sdk or the service account associated with a compute instance cannot be used, because these do not include the private key required to sign the URL. A valid `json` service account credentials key file must be used, as generated via Google cloud console.
> **NOTE** the default google credentials configured by `gcloud` sdk or the service account associated with a compute instance cannot be used, because these do not include the private key required to sign the URL. A valid `json` service account credentials key file must be used, as generated via Google cloud console.

* `content_type` - (Optional) If you specify this in the datasource, the client must provide the `Content-Type` HTTP header with the same value in its request.
* `content_md5` - (Optional) The [MD5 digest](https://cloud.google.com/storage/docs/hashes-etags#_MD5) value in Base64.
Expand Down