aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

[AWS::BedrockAgentCore::Memory] - [BUG] - UserPreferenceMemoryStrategy seems to have return values mistakenly mixed into properties

Open
#2,388 0 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

Other

### Resource Name

AWS::BedrockAgentCore::Memory

### Issue Description

Properties of UserPreferenceMemoryStrategy [currently](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-bedrockagentcore-memory-userpreferencememorystrategy.html) are

```
{
"CreatedAt" : String,
"Description" : String,
"Name" : String,
"Namespaces" : [ String, ... ],
"Status" : String,
"StrategyId" : String,
"Type" : String,
"UpdatedAt" : String
}
```

Many of these are not part of the [UserPreferenceMemoryStrategyInput](https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_UserPreferenceMemoryStrategyInput.html) object of the API but rather seem mixed in common return values (CreatedAt, UpdatedAt) or Memory specific ones (Status, StrategyId)

### Expected Behavior

The properties being limited to the ones of the [UserPreferenceMemoryStrategyInput](https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_UserPreferenceMemoryStrategyInput.html) object

### Observed Behavior

Superfluous properties that do not make sense mixed in

### Test Cases

Look at [definition](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-bedrockagentcore-memory-userpreferencememorystrategy.html)

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the linked CloudFormation definition for AWS::BedrockAgentCore::Memory and compare UserPreferenceMemoryStrategy with the linked UserPreferenceMemoryStrategyInput API object. Done means the strategy properties contain only the input fields and no return-value or Memory-specific fields; the issue names no repository file or local test to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.