Want to contribute to the Setup tasks that run when setting up the workspace

[harlequin]

I want to start looking into the Setup tasks that run when setting up the workspace from the Roadmap.

My idea would be to implement the "tasks" into the workspace.yml file.

With this the end user would have the full flexibility, which they have also inside a project.

@milesj , is it okay to start at this point?
Or do you have an other point of view at this topic?

[milesj]

The tasks themselves wouldn't be configured in workspace.yml, it would just be a list of task targets from existing projects (most likely the root) to run during setup.

[harlequin]

So this means that workspace.yml will get an config Item as vector of strings
which indicates the Tasks to execute?

Do you have already a naming proposal for this config Item?

[milesj]

Yeah just something like this:

setupTasks:
  - 'project:task'

I'm not sure what the name should be.

We also need to figure out what scenarios do these setup tasks actually run.

[harlequin]

We have several use cases for working with this:-

1. Hashicorp Vault Authentication

The workspace shall login into Vault and will derive a token which the sub-projects can use for receiving secrets

2. Conan config install

When using conan as dependency manager for the projects a common config shall be installed and configured on workspace level.

3. Some "preparation" steps shall be executed which will validate the correct environment for the user

For example, has the git config the correct email format and so on ...

4. proto use shall be called to get the tools

Remark:

One big issue we are facing currently is the the option.envfile is evaluated at the very beginning.
Conan and Vault will generate these during runtime ...

A goal from my thinking is that the

• workspace tasks will be executed and generates the dotenv files
• the moon processor for project tasks will evaluate after the SyncWorkspace all the inputs and envFiles

Another approach would be that the proto toolchain feature will be implemented for

• proto
• vault
• conan

What is complicated at this stage is that all 3 tools can be deployed and distributed via toml.
When we want to use the toolchain feature from plugins, these tools have to be converted into wasm,
which from my point of view is a huge overhead compared to the toml approach.

Conclusion:

Guess the main message would be, how can we produce a dotenv before the project tasks will be evaluated?

[milesj]

Guess the main message would be, how can we produce a dotenv before the project tasks will be evaluated?

I don't think you can in a single process, because tasks are expanded (dotenv eval'd) when the action graph is built, not when it is running. This is necessary because env vars are inputs into the cache hash.

You would probably need your users to run moon setup before at some point.

[harlequin]

Got it, moon setup is also called indirectly via toolchains.

So bringing the toolchain proto topic further, would solve my riddle.

Is there any task which I can contribute?

[milesj]

I just landed uv support in proto: https://moonrepo.dev/blog/proto-v0.45#uv

Maybe update the python toolchain to support pip or uv, similar to how node package managers work?