Dagger
Search

engine-dep

relative dependency (`../engine-dep`). Its only purpose is to force the
greeter loader to ALSO resolve another module inside the same remote
repo, mirroring toolchains/java-sdk-dev's `dependencies: [{source:
"../engine-dev"}]` pattern that is suspected to perturb the parent's
context-directory resolution.

Installation

dagger install github.com/dagger/dagger-test-modules/workspace-default-path/engine-dep@ea9f448364a8d3a9278e0de8303fc987f839bbab

Entrypoint

Return Type 
EngineDep
Example
dagger -m github.com/dagger/dagger-test-modules/workspace-default-path/engine-dep@ea9f448364a8d3a9278e0de8303fc987f839bbab call \

func (m *MyModule) Example() *dagger.EngineDep  {
	return dag.
			EngineDep()
}
@function
def example() -> dagger.EngineDep:
	return (
		dag.engine_dep()
	)
@func()
example(): EngineDep {
	return dag
		.engineDep()
}

Types

EngineDep 🔗

ping() 🔗

Ping is a no-op function; it exists so the module has something to expose and the dep load is real.

Return Type 
String !
Example
dagger -m github.com/dagger/dagger-test-modules/workspace-default-path/engine-dep@ea9f448364a8d3a9278e0de8303fc987f839bbab call \
 ping
func (m *MyModule) Example(ctx context.Context) string  {
	return dag.
			EngineDep().
			Ping(ctx)
}
@function
async def example() -> str:
	return await (
		dag.engine_dep()
		.ping()
	)
@func()
async example(): Promise<string> {
	return dag
		.engineDep()
		.ping()
}