Skip to content

Register #[Up] functions as services - #18

Draft
eunomie wants to merge 1 commit into
generate-function-rolefrom
up-function-role
Draft

eunomie wants to merge 1 commit into
generate-function-rolefrom
up-function-role

Conversation

@eunomie

@eunomie eunomie commented Nov 11, 2026

Copy link
Copy Markdown
Member

Stacked on #16. A #[Up] attribute marks a function the engine can run as a service, emitted as .withUp like #[Generate] is as .withGenerator. Validation follows the engine's beta.27 rule (validateUpFunction, core/module.go): the function returns a non-null Service and requires no argument except a Workspace. The e2e fixture gets selfUp(), and generated-entrypoint-call-check asserts dagger start -l lists it (up is a hidden alias of start).

Checks, on the beta.27 engine and CLI: sdk-unit-check passed with a temporary filter including DaggerFunctionTest (202 tests, 321 assertions; the repo's filter does not include it, #13 widens it). generated-entrypoint-call-check passed every assertion up to its last one, which fails on main on beta.27 (fixed in #14).

Not proved: dagger start actually running selfUp.

Signed-off-by: Yves Brissaud <yves@dagger.io>
@eunomie
eunomie added this pull request to stack #32 November 11, 2026 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant