feat: use sparse registry in deployers #773
Merged
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 of change
This switches deployers to use sparse registries, this way each deployer does not need to download the entire index before compiling a project. We might also see some performance gains in CI by switching to sparse registries, I'll try that out as well (hence the draft).
How Has This Been Tested (if applicable)?
I have deployed this to unstable and deploying a service on a fresh deployer takes about 2/3 the time. I am not seeing the new sparse registry progress bar, but we didn't see the progress bar for fetching the entire index either so maybe compiling with the cargo crate doesn't support that. 🤷