Add a cosml.build command to build a project on a cluster

[sjoubert]

This makes use of temporary project in the modeling api, unless we decide to have full support for a persistent Project resource.

Until the modeling api is publicly exposed, babylon creates a temporary port-forward via kubectl.

Design discussion points left open:

• Missing support for the new payload file in the init command, but the actual form of the file will depend of the other discussion points
• Do we need full support for the modapi sub-commands like for the run api? Appart from the build use case it probably won't be used much for now.
• Name of the sub-command group(s): cosml? for separate one-shot commands, modapi/mod-api/modeling-api? for the api command wrappers
• Do we add support for it in apply? It probably needs a toggle to avoid triggering a build each time the project data is applied.
• Do we add first class support for the Project resource or do we keep using a temporary project for now? If we only have a ProjectBuild for now, is the project archive url better placed in a metadata field or as a sidecar.

This is part of a multi repo effort that also involves the terraform modules to have the modeling api deploy in a tenant (Cosmo-Tech/terraform-shared#31, Cosmo-Tech/terraform-tenant#41) and will require the next SDK version (12.3.0)

[sjoubert]

Code has been updated with latest design decisions:

• Remove the separate micro-command and integrate the ProjectBuild resource into the apply macro-command
• I still think that ProjectBuild resources should not be enabled by default, but I didn't find adding a boolean in the yaml file very easy/practical for the whole payload. So for now one has to used the --exclude projectbuild option to avoid rebuilding the project every time. Let me know if that's ok with you or if you want another behavior/way of dealing with that
• The build log behavior is now the following:
  • I've removed the log streaming, build output is only retrieved and handled once the build is complete
  • If the build succeed, the build output is logged at the debug level. So it will be recorded in the babylon log file but not displayed in the terminal (for a standard run at info level)
  • If the build fails, the build output is logged at the error level. So it will be recorded in the babylon log file but also appear in the terminal.

[MohcineTor]

It’s okay for me we can go with this approach for now using --exclude. Later, we can have a quick discussion with the Integration team to see what their preference is.

I also have a quick remark: we could change the order of the steps. We could start with building the project, then move on to organizing the solution, etc. in applay command

[MohcineTor]

👍