OCI's secrets service · portable interface driver.Secrets · OCI index
| Operation | Description |
|---|---|
CreateSecret |
|
DeleteSecret |
|
GetSecret |
|
GetSecretValue |
|
ListSecretVersions |
|
ListSecrets |
|
PutSecretValue |
- AWS Secrets Manager multi-Region replication (
CreateSecretAddReplicaRegions,ReplicateSecretToRegions,RemoveRegionsFromReplication) is control-plane metadata on the primary secret:DescribeSecretreports each replica's Region, KMS key (alias/aws/secretsmanagerwhen none was given),InSyncstatus andReplication succeededmessage, but no replica secret exists in the replica Region. Each Region's mock is independent (andcloudemu servebuilds a Region's state only when that Region is first used), so the primary cannot write into it. Replication completes at once instead of passing throughInProgress. Because no secret here is ever a replica,StopReplicationToReplicaanswersInvalidRequestExceptionfor an existing secret andForceOverwriteReplicaSecrethas nothing to overwrite. A replicated primary can't be deleted until its replicas are removed, as in AWS. A replica Region must have the shape of a Region code (^([a-z]+-)+\d+$, the API model'sRegionTypepattern); cloudemu has no list of real Regions, so a well-formed code that isn't a real Region is still accepted. The messages for a replica Region equal to the primary, a duplicate replica Region and removing a Region that isn't replicated are descriptive; the exception (InvalidParameterException) is unconfirmed against AWS. - AWS Secrets Manager
LastAccessedDateis stamped at day resolution (midnight UTC) byGetSecretValueandBatchGetSecretValue, for the secret only; per-versionLastAccessedDateonListSecretVersionIdsand replicaLastAccessedDateare not tracked. No secret has anOwningService, because no emulated service creates managed secrets. - AWS Secrets Manager
ListSecretswith neitherSortBynorSortOrderlists by name ascending. AWS documentsCreatedDateas the default sort key but not its direction, so the default order is left unchanged; once either field is given,SortBydefaults tocreated-dateandSortOrdertoasc. Values prefixed with!are negation filters. Values within one filter are OR'd, negated ones included, soKey=name,Values=!a,!bmatches every secret whose name lacks either prefix (that is, nearly all of them); to exclude both prefixes, pass twonamefilters, which are AND'd. AWS doesn't document how several negated values combine, and moto ORs them the same way.