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
I noticed this from an issue filed against Pulumi. It doesn't appear to be a Go CDK issue, but the error message wasn't very clear ("The specified blob does not exist") and the user noted that it "doesnt tell which blob it would expect and what content that should have."
Services appear to be inconsistent about whether they include the key name in "not found" errors (see below for details).
Since the portable type (gocloud.dev/blob) knows the key, we should just make sure it's included in the error message for all errors that apply to a key. We already include a prefix, so it's shouldn't be hard to add it there.
I noticed this from an issue filed against Pulumi. It doesn't appear to be a Go CDK issue, but the error message wasn't very clear ("The specified blob does not exist") and the user noted that it "doesnt tell which blob it would expect and what content that should have."
Services appear to be inconsistent about whether they include the key name in "not found" errors (see below for details).
Since the portable type (
gocloud.dev/blob
) knows the key, we should just make sure it's included in the error message for all errors that apply to a key. We already include a prefix, so it's shouldn't be hard to add it there.GCS:
S3:
Azure:
File:
The text was updated successfully, but these errors were encountered: