bug: parity issue in secretsmanager when peforming tags operation #10477
Labels
aws:secretsmanager
AWS Secrets Manager
status: backlog
Triaged but not yet being worked on
type: bug
Bug report
Is there an existing issue for this?
Current Behavior
When we perform the following opeation in sequence, we have a minor parity gap with AWS.
Tags
key in the response, whereas localstack removes the key)Expected Behavior
Tagging operations should be in parity with AWS.
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: