kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

docs: remove dead links. References doesn't exist anymore

Browse Source 
Signed-off-by: jffarge <jf@dagger.io>
This commit is contained in:
jffarge 2022-04-12 14:12:14 +02:00
parent ac59b8c72e
commit dd9a9bab1d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/learn/1008-aws-cloudformation.md
View File

@ -18,7 +18,7 @@ The provisioning strategy detailed below follows S3 best practices. However, to
#### Relays #### Relays
The first thing to consider when developing a plan based on relays is to read their universe reference: it summarizes the expected inputs and their corresponding formats. [Here](../reference/aws/cloudformation.md) is the Cloudformation one. The first thing to consider when developing a plan based on relays is to read their universe reference: it summarizes the expected inputs and their corresponding formats.
## Initialize a Dagger Project and Environment ## Initialize a Dagger Project and Environment
@ -64,7 +64,7 @@ Create a file named `template.cue` and add the following configuration to it.
##### 2. Cloudformation relay ##### 2. Cloudformation relay
As our plan relies on [Cloudformation's relay](../reference/aws/cloudformation.md), let's dissect the expected inputs by gradually incorporating them into our plan. As our plan relies on Cloudformation's relay, let's dissect the expected inputs by gradually incorporating them into our plan.
```shell ```shell
dagger doc alpha.dagger.io/aws/cloudformation dagger doc alpha.dagger.io/aws/cloudformation