We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When trying to put/get an s3 object with key=" " (single space character) the sdk returns the following error:
Unhandled(Unhandled { source: ConstructionFailure(ConstructionFailure { source: InterceptorError { kind: ReadBeforeExecution, interceptor_name: Some("GetObjectEndpointParamsInterceptor"), source: Some(BuildError { kind: MissingField { field: "key", details: "A required field was not set" } }) } }), meta: ErrorMetadata { code: None, message: None, extras: None } })
As I am able to put/get objects with key=" " using the awscli, I should be able to do the same using the rust sdk.
Unable to put/get object with key=" "
let result = s3client .put_object() .bucket("foo") .key(" ") .body(ByteStream::from_static("bar".as_bytes())) .send() .await?;
No response
$ cargo tree | grep aws ├── aws-config v1.5.10 │ ├── aws-credential-types v1.2.1 │ │ ├── aws-smithy-async v1.2.1 │ │ ├── aws-smithy-runtime-api v1.7.3 │ │ │ ├── aws-smithy-async v1.2.1 (*) │ │ │ ├── aws-smithy-types v1.2.9 │ │ ├── aws-smithy-types v1.2.9 (*) │ ├── aws-runtime v1.4.3 │ │ ├── aws-credential-types v1.2.1 (*) │ │ ├── aws-sigv4 v1.2.5 │ │ │ ├── aws-credential-types v1.2.1 (*) │ │ │ ├── aws-smithy-eventstream v0.60.5 │ │ │ │ ├── aws-smithy-types v1.2.9 (*) │ │ │ ├── aws-smithy-http v0.60.11 │ │ │ │ ├── aws-smithy-eventstream v0.60.5 (*) │ │ │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ │ │ ├── aws-smithy-types v1.2.9 (*) │ │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-smithy-async v1.2.1 (*) │ │ ├── aws-smithy-eventstream v0.60.5 (*) │ │ ├── aws-smithy-http v0.60.11 (*) │ │ ├── aws-smithy-runtime v1.7.3 │ │ │ ├── aws-smithy-async v1.2.1 (*) │ │ │ ├── aws-smithy-http v0.60.11 (*) │ │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-types v1.3.3 │ │ │ ├── aws-credential-types v1.2.1 (*) │ │ │ ├── aws-smithy-async v1.2.1 (*) │ │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ │ ├── aws-smithy-types v1.2.9 (*) │ ├── aws-sdk-sso v1.49.0 │ │ ├── aws-credential-types v1.2.1 (*) │ │ ├── aws-runtime v1.4.3 (*) │ │ ├── aws-smithy-async v1.2.1 (*) │ │ ├── aws-smithy-http v0.60.11 (*) │ │ ├── aws-smithy-json v0.60.7 │ │ │ └── aws-smithy-types v1.2.9 (*) │ │ ├── aws-smithy-runtime v1.7.3 (*) │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-types v1.3.3 (*) │ ├── aws-sdk-ssooidc v1.50.0 │ │ ├── aws-credential-types v1.2.1 (*) │ │ ├── aws-runtime v1.4.3 (*) │ │ ├── aws-smithy-async v1.2.1 (*) │ │ ├── aws-smithy-http v0.60.11 (*) │ │ ├── aws-smithy-json v0.60.7 (*) │ │ ├── aws-smithy-runtime v1.7.3 (*) │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-types v1.3.3 (*) │ ├── aws-sdk-sts v1.50.0 │ │ ├── aws-credential-types v1.2.1 (*) │ │ ├── aws-runtime v1.4.3 (*) │ │ ├── aws-smithy-async v1.2.1 (*) │ │ ├── aws-smithy-http v0.60.11 (*) │ │ ├── aws-smithy-json v0.60.7 (*) │ │ ├── aws-smithy-query v0.60.7 │ │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-smithy-runtime v1.7.3 (*) │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-smithy-xml v0.60.9 │ │ ├── aws-types v1.3.3 (*) │ ├── aws-smithy-async v1.2.1 (*) │ ├── aws-smithy-http v0.60.11 (*) │ ├── aws-smithy-json v0.60.7 (*) │ ├── aws-smithy-runtime v1.7.3 (*) │ ├── aws-smithy-runtime-api v1.7.3 (*) │ ├── aws-smithy-types v1.2.9 (*) │ ├── aws-types v1.3.3 (*) ├── aws-sdk-s3 v1.62.0 │ ├── aws-credential-types v1.2.1 (*) │ ├── aws-runtime v1.4.3 (*) │ ├── aws-sigv4 v1.2.5 (*) │ ├── aws-smithy-async v1.2.1 (*) │ ├── aws-smithy-checksums v0.60.13 │ │ ├── aws-smithy-http v0.60.11 (*) │ │ ├── aws-smithy-types v1.2.9 (*) │ ├── aws-smithy-eventstream v0.60.5 (*) │ ├── aws-smithy-http v0.60.11 (*) │ ├── aws-smithy-json v0.60.7 (*) │ ├── aws-smithy-runtime v1.7.3 (*) │ ├── aws-smithy-runtime-api v1.7.3 (*) │ ├── aws-smithy-types v1.2.9 (*) │ ├── aws-smithy-xml v0.60.9 (*) │ ├── aws-types v1.3.3 (*) ├── aws-smithy-runtime-api v1.7.3 (*) │ ├── aws-credential-types v1.2.1 (*) │ ├── aws-sdk-iam v1.52.0 │ │ ├── aws-credential-types v1.2.1 (*) │ │ ├── aws-runtime v1.4.3 (*) │ │ ├── aws-smithy-async v1.2.1 (*) │ │ ├── aws-smithy-http v0.60.11 (*) │ │ ├── aws-smithy-json v0.60.7 (*) │ │ ├── aws-smithy-query v0.60.7 (*) │ │ ├── aws-smithy-runtime v1.7.3 (*) │ │ ├── aws-smithy-runtime-api v1.7.3 (*) │ │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-smithy-xml v0.60.9 (*) │ │ ├── aws-types v1.3.3 (*) │ ├── aws-sigv4 v1.2.5 (*) │ ├── aws-smithy-types v1.2.9 (*) │ │ ├── aws-smithy-types v1.2.9 (*) ├── aws-config v1.5.10 (*) ├── aws-credential-types v1.2.1 (*) ├── aws-sdk-s3 v1.62.0 (*) ├── aws-smithy-runtime-api v1.7.3 (*) │ │ │ ├── aws-credential-types v1.2.1 (*) │ │ │ ├── aws-sdk-iam v1.52.0 (*) │ │ │ ├── aws-sdk-s3 v1.62.0 (*) │ │ │ ├── aws-sigv4 v1.2.5 (*) │ │ │ ├── aws-smithy-types v1.2.9 (*) │ ├── aws-credential-types v1.2.1 (*)
linux x64
The text was updated successfully, but these errors were encountered:
Hey @nberrington-cloudian, thanks for submitting this issue. We'll add it to our backlog.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
When trying to put/get an s3 object with key=" " (single space character) the sdk returns the following error:
Regression Issue
Expected Behavior
As I am able to put/get objects with key=" " using the awscli, I should be able to do the same using the rust sdk.
Current Behavior
Unable to put/get object with key=" "
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
Version
Environment details (OS name and version, etc.)
linux x64
Logs
No response
The text was updated successfully, but these errors were encountered: