Skip to content

Latest commit

 

History

History
22 lines (17 loc) · 2.71 KB

vault.md

File metadata and controls

22 lines (17 loc) · 2.71 KB

Vault

OCI's secrets service · portable interface driver.Secrets · OCI index

Operations (7)

Operation Description
CreateSecret
DeleteSecret
GetSecret
GetSecretValue
ListSecretVersions
ListSecrets
PutSecretValue

Not in scope

  • AWS Secrets Manager multi-Region replication (CreateSecret AddReplicaRegions, ReplicateSecretToRegions, RemoveRegionsFromReplication) is control-plane metadata on the primary secret: DescribeSecret reports each replica's Region, KMS key (alias/aws/secretsmanager when none was given), InSync status and Replication succeeded message, but no replica secret exists in the replica Region. Each Region's mock is independent (and cloudemu serve builds 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 through InProgress. Because no secret here is ever a replica, StopReplicationToReplica answers InvalidRequestException for an existing secret and ForceOverwriteReplicaSecret has 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's RegionType pattern); 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 LastAccessedDate is stamped at day resolution (midnight UTC) by GetSecretValue and BatchGetSecretValue, for the secret only; per-version LastAccessedDate on ListSecretVersionIds and replica LastAccessedDate are not tracked. No secret has an OwningService, because no emulated service creates managed secrets.
  • AWS Secrets Manager ListSecrets with neither SortBy nor SortOrder lists by name ascending. AWS documents CreatedDate as the default sort key but not its direction, so the default order is left unchanged; once either field is given, SortBy defaults to created-date and SortOrder to asc. Values prefixed with ! are negation filters. Values within one filter are OR'd, negated ones included, so Key=name,Values=!a,!b matches every secret whose name lacks either prefix (that is, nearly all of them); to exclude both prefixes, pass two name filters, which are AND'd. AWS doesn't document how several negated values combine, and moto ORs them the same way.