EgressInfo helpers

[frostbyte73]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: bb036e3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[biglittlebigben]

How will we communicate the case where a segmented file egress eventually ended as failure, but where some segments have failed to upload as well? Customers may want to download whatever segments are available, but will need a way to see that some are only available on the backup storage.

What I'm getting at is that I'm wondering if backup status should be orthogonal to the egress status/error state.

[frostbyte73]

True, I think we'll need to add something else because even a separate backup_used state wouldn't cover that