Skip to content

Commit

Permalink
Use s3:// protocol schema for artifact examples
Browse files Browse the repository at this point in the history
Per the discussion in #15123,
we're going to use the explicit s3 protocol in the examples since that
is the likeliest to work in all scenarios
  • Loading branch information
Thomas Wunderlich committed Nov 7, 2022
1 parent 1b19180 commit 282d8ba
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions website/content/docs/job-specification/artifact.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@ This example uses path-based notation on a publicly-accessible bucket:

```hcl
artifact {
source = "my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
}
```

Expand Down Expand Up @@ -240,7 +240,7 @@ Alternatively you can use virtual hosted style:

```hcl
artifact {
source = "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
}
```

Expand Down

0 comments on commit 282d8ba

Please sign in to comment.