s3Client.getBucketEncryption(bucketName).getServerSideEncryptionConfiguration().getRules()
returns a List<ServerSideEncryptionRule>
. Since there are no option of selection multiple Server Side Encryptions (The console has a radio button to select between various encryption types), why a list of Rules with just element is returned. Would it not have been a better API design to just return a ServerSideEncryptionRule
instead of a list ?
Hey All,
I'm trying to create a signed request to use in the vault-java-driver (https://github.com/BetterCloud/vault-java-driver/blob/fef74b881b9f3620b68759f1b0d297591f80975e/src/main/java/com/bettercloud/vault/api/Auth.java#L838-L917)
What's the correct way to go about creating a signed request and passing along the signed data?
Using the golang SDK you could just create a request objet and then call ..sign
on it. I was hoping there would be something similar in Java.
@DynamoDBTable(tableName = "ignored")
data class PendingOrder(
@DynamoDBHashKey
var PK: String? = null,
@DynamoDBRangeKey
@DynamoDBIndexRangeKey(globalSecondaryIndexName = "pendingOrders")
var createdAt: String? = null,
@DynamoDBIndexHashKey(globalSecondaryIndexName = "pendingOrders")
var pending: Int? = null,
...
)
open fun findPendingOrders(createdAt: String): List<PendingOrder>? {
val expression = DynamoDBQueryExpression<PendingOrder>()
.withConsistentRead(false)
.withIndexName("pendingOrders")
.withKeyConditionExpression("pending = :pending AND createdAt < :createdAt")
.withExpressionAttributeValues(
mapOf(
":pending" to AttributeValue().withN("1"),
":createdAt" to AttributeValue(createdAt)
)
)
return mapper.query(PendingOrder::class.java, expression)
}
PendingOrder; no mapping for HASH key: com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMappingException
com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMappingException: PendingOrder; no mapping for HASH key
@DynamoDBTable(tableName = "ignored")
data class PendingOrder(
@get:DynamoDBHashKey(attributeName = "PK")
var PK: String? = null,
@get:DynamoDBRangeKey
@get:DynamoDBIndexRangeKey(globalSecondaryIndexName = "pendingOrders")
var createdAt: String? = null,
@get:DynamoDBIndexHashKey(globalSecondaryIndexName = "pendingOrders")
var pending: Int? = null,
WebIdentityTokenCredentialsProvider
. I thought I'd try backporting WebIdentityTokenCredentialsProvider
and related classes to the same version that Hadoop depends on and provide a custom build. That might make things work as I need. Does this sound like a reasonable thing to do? :)