[Storage] set/get_access_policy for ContainerClient
#3303
Conversation
vincenttran-msft
changed the title
set/get_access_policy for ContainerClient
| response_access_policy.clone().unwrap().permission, | ||
| access_policy.permission | ||
| ); | ||
| assert_eq!(response_access_policy.clone().unwrap().expiry, expiry); |
There was a problem hiding this comment.
log
Relevant log excerpt:
2025-11-07T02:41:40.3347517Z ---- test_container_access_policy stdout ----
2025-11-07T02:41:40.3347746Z
2025-11-07T02:41:40.3348185Z thread 'test_container_access_policy' (20747) panicked at sdk/storage/azure_storage_blob/tests/blob_container_client.rs:449:5:
2025-11-07T02:41:40.3348696Z assertionleft == rightfailed
2025-11-07T02:41:40.3349477Z left: Some("2025-11-07T02:09:40.3229246Z")
2025-11-07T02:41:40.3353978Z right: Some("2025-11-07T02:41:35.2937819Z")
@heaths We are running into an issue when asserting against dynamically generated datetime objects, as here the LHS is from the recording: <Expiry>2025-11-07T02:09:40.3229246Z</Expiry>
while the RHS is from the actual test execution.
In Python, this is resolved through using a get_datetime_variable function:
expiry_time = self.get_datetime_variable(variables, 'expiry_time', datetime.utcnow() + timedelta(hours=1))
And this way the datetimes are present in variables:
"Variables": {
"expiry_time": "2022-08-09T19:54:43.709865",
Is this something that can be done in Rust currently, or is this a net new feature for Rust's test infrastructure? I see that we have var() and var_opt() but both of these are for getting and not setting.
1 participant
.tsp: Azure/azure-rest-api-specs#38633set_access_policy()andget_access_policy()HashMap<String, AccessPolicy>->SignedIdentifiers