Return actual build id when requesting build on another node #1321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #1313
This PR returns the actual build ID to the Pyrsia CLI when the build command was used and the actual build was triggered on a different Pyrsia node instead of the local Pyrsia node.
Steps to test
Follow the procedure described in Pyrsia demo: build Docker images from source. When triggering a build from source from node B (aka the node that was not authorized) using the pyrsia CLI, it should print a UUID instead of a regular number:
PR Checklist
Code Contributions
cargo build --all-targets
successfully.cargo test --workspace
and everything passes.