You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When pointing OPA to fetch bundles from an endpoint that doesn't serve bundles (likely due to typo or misconfiguration in the remote), the error message looks like this:
This has led many users to believe there is something wrong with the bundle packaging itself, leading them to debug the bundle creation process, when the real problem is that the remote doesn't serve the bundle in the first place.
It would be good if we printed this error message only when a broken bundle was served. If we can't differentiate, we might want to print just something like "no bundle found at remote or invalid bundle format".
The text was updated successfully, but these errors were encountered:
I think we can improve the error message by looking at the Content-Type response header. If it isn't application/octet-stream (as a tarball is just binary data) but something like text/html, we can print a more informative message.
When pointing OPA to fetch bundles from an endpoint that doesn't serve bundles (likely due to typo or misconfiguration in the remote), the error message looks like this:
This has led many users to believe there is something wrong with the bundle packaging itself, leading them to debug the bundle creation process, when the real problem is that the remote doesn't serve the bundle in the first place.
It would be good if we printed this error message only when a broken bundle was served. If we can't differentiate, we might want to print just something like "no bundle found at remote or invalid bundle format".
The text was updated successfully, but these errors were encountered: