ModuleSource

No description

No description

Load the source as a module. If this is a local source, the parent directory must have been provided during module source creation

A human readable ref string representation of this module source.

The blueprint referenced by the module source.

The client-facing introspection schema JSON file for this module source.

This is the schema consumed by client codegen: unlike introspectionSchemaJSON (the module-facing schema), it hides no core types and installs this module (reached via dag.) so a generated client can bind it. The module's dependencies are excluded: a client is generated for a single module plus core, not its dependency graph.

The ref to clone the root of the git repo from. Only valid for git sources.

The resolved commit of the git repo this source points to.

The clients generated for the module.

Whether an existing module config file was found.

The full directory loaded for the module source, including the source code as a subdirectory.

The dependencies of the module source.

A content-hash of the module source. Module sources with the same digest will output the same generated context and convert into the same module instance.

The directory containing the module configuration and source code (source code may be in a subdir).

The engine version of the module.

The generated files and directories made on top of the module source's context directory, returned as a Changeset.

The generated files and directories made on top of the module source's context directory.

The URL to access the web view of the repository (e.g., GitHub, GitLab, Bitbucket).

The URL to the source's git repo in a web browser. Only valid for git sources.

A unique identifier for this ModuleSource.

The introspection schema JSON file for this module source.

This file represents the schema visible to the module's source code, including all core types and those from the dependencies.

Note: this is in the context of a module, so some core types may be hidden.

The kind of module source (currently local, git or dir).

The full absolute path to the context directory on the caller's host filesystem that this module source is loaded from. Only valid for local module sources.

The name of the module, including any setting via the withName API.

The original name of the module as read from the module config file (or set for the first time with the withName API).

The original subpath used when instantiating this module source, relative to the context directory.

The pinned version of this module source.

The import path corresponding to the root of the git repo this source points to. Only valid for git sources.

The SDK configuration of the module.

The path, relative to the context directory, that contains the module config.

The path to the directory containing the module's source code, relative to the context directory.

Forces evaluation of the module source, including any loading into the engine and associated validation.

The toolchains referenced by the module source.

The module's dagger.json with any in-memory edits from with* APIs applied, as a diff relative to the source's context directory.

Unlike generatedContextDirectory, this does not run codegen and does not validate the engine version against the running engine, so it can be used to declare an engine requirement newer than the running engine. Loading or serving such a module still fails at moduleSource.asModule.

User-defined defaults read from local .env files

The specified version of the git repo this source points to.

Set a blueprint for the module source.

Update the module source with a new client to generate.

Append the provided dependencies to the module source's dependency list.

Upgrade the engine version of the module to the given value.

Enable the experimental features for the module source.

Update the module source with additional include patterns for files+directories from its context that are required for building it

Update the module source with a new name.

Update the module source with a new SDK.

Update the module source with a new source subpath.

Add toolchains to the module source.

Update the blueprint module to the latest version.

Update one or more module dependencies.

Update one or more toolchains.

Update one or more clients.

Remove the current blueprint from the module source.

Remove a client from the module source.

Remove the provided dependencies from the module source's dependency list.

Disable experimental features for the module source.

Remove the provided toolchains from the module source.