Built-in check for generate functions

[eunomie]

Currently we have one single function in .dagger main module that runs all the generate functions and ensure the result is empty.
Those changes handle that in the engine: all generate functions are now automatically handled as a check function. When they are run, it will succeed if the resulting changeset is empty.

This allows to always ensure all generated functions are correctly run on CI, without to introduce a new module or concept.
Just declare your checks and generates and both dagger generate and dagger checks will work.

You can still use dagger check --no-generate if you don't want to include the generate functions.

$ dagger check -l

Name                                         Description
ci:bootstrap                                 Build dagger from source, and check that it can bootstrap its own CI
cli:release-dry-run                          Verify that the CLI builds without actually publishing anything
docs:lint-markdown                           Lint documentation files
elixir-sdk:codegen-test                      Run dagger_codegen tests
elixir-sdk:lint                              Lint the SDK
elixir-sdk:release-dry-run                   Test the publishing process
elixir-sdk:sdk-test                          Run the SDK tests
...
typescript-sdk:test-nodejs-lts               Test the SDK with LTS version of Node
typescript-sdk:test-nodejs-prev-lts          Test the SDK with previous LTS version of Node

Generators
changelog:generate                           Generate the changelog with 'changie merge'. Only run this manually, at release time.
docs:references                              Regenerate the API schema and CLI reference docs
engine-dev:generate                          Generate any engine-related files
go-sdk:generate                              Regenerate the Go SDK API
...

[idlsoft]

If I understand it correctly this turns all +generate functions into +check functions.
It may be useful to have some granular control over it.
For example if generated files are not committed, a check would fail, right?

[eunomie]

For example if generated files are not committed, a check would fail, right?

Yes, but that's exactly the purpose of generate functions, to generate files that should be committed.
On dagger/dagger for instance we always have a check that runs all the generate functions and check it's empty. It's just that but better, more explicit, and more control on top of it as it allows to dagger check my-generate-function as it wasn't possible previously.

[kpenfound]

LGTM. Some conflicts though

[eunomie]

I'm merging the PR:

• ✔️ cli:release-dry-run manually validated
• ✔️ engine-dev:release-dry-run manually validated
• ✔️ dagger-dev:generated manually validated

Once dagger cloud will run on a version including those changes, we will be able to fully remove the engine-dev:generated check as it will be a duplication of the built-in checks.