ensure artifacts folder exists when deploying rust bindings #5588
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.
Summary
When deploying the rust binding packages, if the download-artifacts step fails to download any artifacts, it will not raise an error. Neither will the npm publish step. This will lead to problems where the packages depending on the bindings will be broken since the bindings will not get released.
This PR adds a basic sanity check to make sure that some artifacts are downloaded, otherwise it will fail.
Closes IFL-2719
Testing Plan
Temporarily added this step into a different CI job to ensure it works as expected.
Documentation
N/A
Breaking Change
N/A