You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/current_docs/configuration/cloud.mdx
+72-9Lines changed: 72 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,15 @@ Dagger Cloud requires a GitHub or Google account for identity verification. If y
15
15
Dagger Cloud requires Dagger v0.11 or higher.
16
16
:::
17
17
18
-
## Traces
18
+
## Organizations
19
+
20
+
A Dagger Cloud "organization" refers to a group of member accounts linked to a single team.
21
+
22
+
A member account grants a person access to log in to a Dagger Cloud organization to diagnose workflow failures and collaborate on changes. Deleting a member of a Dagger Cloud organization will not remove their runs and changes from Dagger Cloud.
23
+
24
+
:::important
25
+
You must hold the `Admin` role of a Dagger Cloud organization to administer members. You cannot change a member's role. Please contact Dagger Support via the in-app messenger for assistance if you need to change a member's role.
1. You will then enter your payment information. After your free 14 day trial completes, you will be automatically subscribed to the Dagger Cloud Team plan.
37
45
38
-
1. Click `Go to dashboard`. The next step walks you through how to send telemetry to Dagger Cloud.
To connect to Dagger Cloud from a CI environment, you require a Dagger Cloud token. Dagger Cloud creates this token automatically when you sign up.
74
82
75
-
To find your token, navigate to the organization settings page using the cogwheel icon in the top navigation bar. Under the `Tokens` sub-menu, click the eye icon to view the token. You can also use this URL pattern: `https://v3.dagger.cloud/{Your Org Name}/settings?tab=Tokens`
83
+
To find your token, navigate to the settings page using the cogwheel icon in the top navigation bar. Under the `Tokens` sub-menu, click the eye icon to view the token. You can also use this URL pattern: `https://v3.dagger.cloud/{Your Org Name}/settings?tab=Tokens`
@@ -200,16 +208,71 @@ Dagger Cloud automatically detects if the traces produced by your workflows orig
200
208
a CI system and a public repository. When both conditions are met, Dagger Cloud allows
201
209
public access to these traces without requiring an invitation to the organization.
202
210
203
-
To modify this default setting, navigate to the organization settings page using the cogwheel icon in the top navigation bar. Under the `Visibility` sub-menu, click the eye icon to toggle public access to trace data as needed.
211
+
To modify this default setting, navigate to the organization page using the cogwheel icon in the top navigation bar. Under the `Visibility` sub-menu, click the eye icon to toggle public access to trace data as needed.
A member account grants a person access to log in to a Dagger Cloud organization to diagnose workflow failures and collaborate on changes. Deleting a member of a Dagger Cloud organization will not remove their runs and changes from Dagger Cloud.
217
+
Dagger Cloud lets you see all your organization's modules in one place, with metadata like engine versions, descriptions, and linked repositories. Module information and activity is automatically synced from GitHub.
210
218
211
-
:::important
212
-
You must hold the `Admin` role of a Dagger Cloud organization to administer members. You cannot change a member's role. Please contact Dagger Support via the in-app messenger for assistance if you need to change a member's role. This functionality is coming soon.
219
+
### Add modules
220
+
221
+
Dagger Cloud scans your specified repositories for Dagger modules, showing them automatically in Dagger Cloud.
222
+
223
+
:::info
224
+
You must be signed in to Dagger Cloud with GitHub.
225
+
:::
226
+
227
+
To initiate this process, navigate to the organization page using the cogwheel icon in the top navigation bar and select the `Git Sources` sub-menu. Click `Install the GitHub Application` to add a GitHub account or organization.
Complete the process and then, once the GitHub account or organization appears in the Dagger Cloud user interface, click `Enable module scanning` to have Dagger Cloud begin scanning for Dagger modules. You can enable module scanning for multiple GitHub organizations. Each one can be enabled on a single Dagger organization.
You can view your entire list of modules by selecting the `All Modules` tab. If you wish to curate and organize this list, you can create custom views of modules filtered by team, service, or domain. To create a custom view, click the `+` icon.
This information is available for all versions of the module; use the version selector in the top bar to switch between versions.
213
276
:::
214
277
215
278
## Roles and permissions
@@ -227,6 +290,6 @@ You cannot change a member's role at this time. Please contact Dagger via the su
227
290
228
291
## Cache pruning
229
292
230
-
Within a Dagger Cloud organization, it is possible to prune the Dagger Cloud cache for a specific token. Navigate to the organization settings page using the cogwheel icon in the top navigation bar, select the `Tokens` sub-menu, and click the broom icon for the corresponding token.
293
+
Within a Dagger Cloud organization, it is possible to prune the Dagger Cloud cache for a specific token. Navigate to the organization page using the cogwheel icon in the top navigation bar, select the `Tokens` sub-menu, and click the broom icon for the corresponding token.
Modules integrate seamlessly with Dagger Cloud, which offers a collaborative environment to manage modules, visualize dependencies, and trace executions.
48
+
49
+
- A dedicated "Modules" tab in Dagger Cloud: See all your organization’s modules in one place, with metadata like engine versions, descriptions, and linked repositories, automatically pulled and synced from GitHub.
50
+
- Views for better organization: Create filtered views of modules by team, service, or domain.
51
+
- Documentation: See API documentation for each module and version, directly in the Dagger Cloud dashboard.
52
+
- Version-aware navigation: View active branches and tags, ordered by recency.
53
+
- Supply chain visibility: See exactly which modules your code depends on, and which depend on yours. This upstream/downstream awareness helps eliminate breakage and fosters stronger collaboration between teams.
54
+
- Trace-to-module linkage: Trace failed runs or AI workflows back to the exact module versions that caused them.
To make it easier to search and consume Dagger modules, the [Daggerverse](https://daggerverse.dev) is a free service run by Dagger, which indexes all publicly available Dagger modules. These might be Dagger modules developed by your team, your organization or the broader Dagger community. By importing and reusing these Dagger modules in your workflows and across your teams, you can significantly speed up development.
46
61
47
62
## Learn more
@@ -50,4 +65,5 @@ To make it easier to search and consume Dagger modules, the [Daggerverse](https:
50
65
-[Call a remote module](../api/remote-modules.mdx)
0 commit comments