aws-sdk-rust
aws-sdk-rust copied to clipboard
us-east-1 missing from BucketLocationConstraint ENUM
Describe the bug
in aws_sdk_s3::types::BucketLocationConstraint us-east-1 is missing.
Expected Behavior
I assume it should be in the enum
Current Behavior
not there.
Reproduction Steps
Looking over the source code
Possible Solution
No response
Additional Information/Context
Maybe I am missing something, or unclear on how to create a BucketLocationConstraint for us-east-1
Version
aws-test v0.1.0 (/home/dtoebe/Projects/aws-test)
├── aws-config v0.56.1
│ ├── aws-credential-types v0.56.1
│ │ ├── aws-smithy-async v0.56.1
│ │ ├── aws-smithy-types v0.56.1
│ ├── aws-http v0.56.1
│ │ ├── aws-credential-types v0.56.1 (*)
│ │ ├── aws-smithy-http v0.56.1
│ │ │ ├── aws-smithy-eventstream v0.56.1
│ │ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ ├── aws-smithy-types v0.56.1 (*)
│ │ ├── aws-types v0.56.1
│ │ │ ├── aws-credential-types v0.56.1 (*)
│ │ │ ├── aws-smithy-async v0.56.1 (*)
│ │ │ ├── aws-smithy-client v0.56.1
│ │ │ │ ├── aws-smithy-async v0.56.1 (*)
│ │ │ │ ├── aws-smithy-http v0.56.1 (*)
│ │ │ │ ├── aws-smithy-http-tower v0.56.1
│ │ │ │ │ ├── aws-smithy-http v0.56.1 (*)
│ │ │ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ │ ├── aws-smithy-http v0.56.1 (*)
│ │ │ ├── aws-smithy-types v0.56.1 (*)
│ ├── aws-sdk-sso v0.30.0
│ │ ├── aws-credential-types v0.56.1 (*)
│ │ ├── aws-http v0.56.1 (*)
│ │ ├── aws-runtime v0.56.1
│ │ │ ├── aws-credential-types v0.56.1 (*)
│ │ │ ├── aws-http v0.56.1 (*)
│ │ │ ├── aws-sigv4 v0.56.1
│ │ │ │ ├── aws-smithy-eventstream v0.56.1 (*)
│ │ │ │ ├── aws-smithy-http v0.56.1 (*)
│ │ │ ├── aws-smithy-async v0.56.1 (*)
│ │ │ ├── aws-smithy-eventstream v0.56.1 (*)
│ │ │ ├── aws-smithy-http v0.56.1 (*)
│ │ │ ├── aws-smithy-runtime-api v0.56.1
│ │ │ │ ├── aws-smithy-async v0.56.1 (*)
│ │ │ │ ├── aws-smithy-http v0.56.1 (*)
│ │ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ │ ├── aws-types v0.56.1 (*)
│ │ ├── aws-smithy-async v0.56.1 (*)
│ │ ├── aws-smithy-client v0.56.1 (*)
│ │ ├── aws-smithy-http v0.56.1 (*)
│ │ ├── aws-smithy-json v0.56.1
│ │ │ └── aws-smithy-types v0.56.1 (*)
│ │ ├── aws-smithy-runtime v0.56.1
│ │ │ ├── aws-smithy-async v0.56.1 (*)
│ │ │ ├── aws-smithy-client v0.56.1 (*)
│ │ │ ├── aws-smithy-http v0.56.1 (*)
│ │ │ ├── aws-smithy-runtime-api v0.56.1 (*)
│ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ ├── aws-smithy-runtime-api v0.56.1 (*)
│ │ ├── aws-smithy-types v0.56.1 (*)
│ │ ├── aws-types v0.56.1 (*)
│ ├── aws-sdk-sts v0.30.0
│ │ ├── aws-credential-types v0.56.1 (*)
│ │ ├── aws-http v0.56.1 (*)
│ │ ├── aws-runtime v0.56.1 (*)
│ │ ├── aws-smithy-async v0.56.1 (*)
│ │ ├── aws-smithy-client v0.56.1 (*)
│ │ ├── aws-smithy-http v0.56.1 (*)
│ │ ├── aws-smithy-json v0.56.1 (*)
│ │ ├── aws-smithy-query v0.56.1
│ │ │ ├── aws-smithy-types v0.56.1 (*)
│ │ ├── aws-smithy-runtime v0.56.1 (*)
│ │ ├── aws-smithy-runtime-api v0.56.1 (*)
│ │ ├── aws-smithy-types v0.56.1 (*)
│ │ ├── aws-smithy-xml v0.56.1
│ │ ├── aws-types v0.56.1 (*)
│ ├── aws-smithy-async v0.56.1 (*)
│ ├── aws-smithy-client v0.56.1 (*)
│ ├── aws-smithy-http v0.56.1 (*)
│ ├── aws-smithy-http-tower v0.56.1 (*)
│ ├── aws-smithy-json v0.56.1 (*)
│ ├── aws-smithy-types v0.56.1 (*)
│ ├── aws-types v0.56.1 (*)
├── aws-credential-types v0.56.1 (*)
├── aws-sdk-s3 v0.30.0
│ ├── aws-credential-types v0.56.1 (*)
│ ├── aws-http v0.56.1 (*)
│ ├── aws-runtime v0.56.1 (*)
│ ├── aws-sigv4 v0.56.1 (*)
│ ├── aws-smithy-async v0.56.1 (*)
│ ├── aws-smithy-checksums v0.56.1
│ │ ├── aws-smithy-http v0.56.1 (*)
│ │ ├── aws-smithy-types v0.56.1 (*)
│ ├── aws-smithy-client v0.56.1 (*)
│ ├── aws-smithy-eventstream v0.56.1 (*)
│ ├── aws-smithy-http v0.56.1 (*)
│ ├── aws-smithy-json v0.56.1 (*)
│ ├── aws-smithy-runtime v0.56.1 (*)
│ ├── aws-smithy-runtime-api v0.56.1 (*)
│ ├── aws-smithy-types v0.56.1 (*)
│ ├── aws-smithy-xml v0.56.1 (*)
│ ├── aws-types v0.56.1 (*)
├── aws-types v0.56.1 (*)
Environment details (OS name and version, etc.)
Ubuntu 23.04
Logs
No response
You can use BucketLocationConstraint::from("us-east-1") to create (any) string-enum in the Rust SDK from an arbitrary string. That said, I think we need to improve our generated docs on creating enums, currently they're really focused on matching.
To add, BucketLocationConstraint for us-east-1 is intentionally not included in an S3 model (from which aws_sdk_s3 is derived).
You can also see that the location constraint for us-east-1 is treated in a special way compared to other regions.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.