Change Details

If {T356262} is in, then we can add the subcommands: ``` > toolforge deploy <path-to-yaml> # deploys everything in the given yaml, updating the tool config > toolforge status # shows info about the current deployed config and the running jobs/builds/etc. ``` Otherwise start with a small subclient (ex. `toolforge-component`) until we can merge all of them. ``` > toolforge component deploy <path-to-yaml> > toolforge component status ```

Start with a small subclient (ex. `toolforge-component`) until we can merge all of them. ``` > toolforge component deploy <path-to-yaml> > toolforge component status ``` Possible output: ``` $ toolforge component deploy mytool.yaml Starting deploy for toolhunt v1.0.0... Building images: [✅] toolhunt-ui [✅] toolhunt-api All components deployed $ toolforge component status # very speculative Current components: ------------------------------------------- name status build-id ------------------------------------------- toolhunt-ui RUNNING build-id-12345 toolhunt-api RUNNING build-id-12344 toolhunt-flower ERROR build-id-12344 Last triggered builds: # similar to `toolforge build list` with deployment info ----------------------------------------------------------------------------------------- build time | status | build id | component | trigger ----------------------------------------------------------------------------------------- 2024-04-04 12:11:00 UTC | RUNNING | build-id-12345 | toolhunt-ui | triggered manually 2024-04-04 12:00:00 UTC | OK | build-id-12344 | toolhunt-api | triggered manually ```

If {T356262} is in,Start with a small subclient (ex. then`toolforge-component`) until we can add the subcommands:merge all of them. ``` > toolforge deploy <path-to-yaml> # deploys everything in the given yaml, updating the tool config > toolforge status # shows info about the current deployed config and the running jobs/builds/etc.component deploy <path-to-yaml> > toolforge component status ``` Otherwise start with a small subclient (ex. `toolforge-component`) until we can merge all of them.Possible output: ``` >$ toolforge component deploy <path-to-mytool.yaml> > toolforge component statusStarting deploy for toolhunt v1.0.0... ```Building images: [✅] toolhunt-ui [✅] toolhunt-api All components deployed $ toolforge component status # very speculative Current components: ------------------------------------------- name status build-id ------------------------------------------- toolhunt-ui RUNNING build-id-12345 toolhunt-api RUNNING build-id-12344 toolhunt-flower ERROR build-id-12344 Last triggered builds: # similar to `toolforge build list` with deployment info ----------------------------------------------------------------------------------------- build time | status | build id | component | trigger ----------------------------------------------------------------------------------------- 2024-04-04 12:11:00 UTC | RUNNING | build-id-12345 | toolhunt-ui | triggered manually 2024-04-04 12:00:00 UTC | OK | build-id-12344 | toolhunt-api | triggered manually ```