Skip to content

Commit 32b07da

Browse files
authored
document how to try ee version on saas (#2119)
1 parent ddc69dd commit 32b07da

File tree

2 files changed

+34
-1
lines changed

2 files changed

+34
-1
lines changed

docs/ee/saas.mdx

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: "Try Digger EE on Cloud"
3+
---
4+
5+
Digger Enterprise Edition is available as a SaaS offering. You can try it out for free by signing up at [ui.digger.dev](https://ui.digger.dev).
6+
The best quickstart for this is either the self-guided tour on the website or the quickstart pages found here:
7+
8+
- [terraform](/ce/getting-started/with-terraform)
9+
- [opentofu](/ce/getting-started/with-opentofu)
10+
- [terragrunt](/ce/getting-started/with-terragrunt)
11+
12+
Since the backend hosted on ui.digger.dev is based on the EE image it will enable you to trial the EE functions. Once you have
13+
the basic version of the workflow running you can [request a license key](https://digger.dev) by speaking to the team and update
14+
it in the digger_workflow.yml step like so:
15+
16+
```
17+
- uses: diggerhq/digger@vLatest
18+
with:
19+
digger-spec: ${{ inputs.spec }}
20+
# ...
21+
ee: 'true'
22+
env:
23+
GITHUB_CONTEXT: ${{ toJson(github) }}
24+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
25+
DIGGER_LICENSE_KEY: ${{ secrets.DIGGER_LICENSE_KEY }}
26+
```
27+
28+
The key changes is passing `ee: true` and the license key as an env variable to the workflow. You can then proceed to perform improvements to the workflow as seen fit.
29+
30+
31+
32+

docs/mint.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,8 @@
6161
"ee/buildkite",
6262
"ee/fips-140",
6363
"ee/ai-summaries",
64-
"ee/remote-jobs"
64+
"ee/remote-jobs",
65+
"ee/saas"
6566
]
6667
},
6768
{

0 commit comments

Comments
 (0)