Skip to content

feat: Add CMK support in atlas-create-cluster - #1380

Merged
manupedrozo merged 1 commit into
mainfrom
CLOUDP-407393-create-cluster-cmk-support
Jul 24, 2026
Merged

feat: Add CMK support in atlas-create-cluster#1380
manupedrozo merged 1 commit into
mainfrom
CLOUDP-407393-create-cluster-cmk-support

Conversation

@manupedrozo

@manupedrozo manupedrozo commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Description

Add encryption at rest via customer-managed key support to the atlas-create-cluster tool.

  • The selected CMK provider must already have a valid encryption at rest configuration in the project.
  • Defaults to the cluster's provider if a valid configuration exists.

Ticket: CLOUDP-407393

Checklist

@manupedrozo manupedrozo added the no-title-validation Add this label to disable the title check for this PR. label Jul 22, 2026
@manupedrozo
manupedrozo marked this pull request as ready for review July 23, 2026 07:57
@manupedrozo
manupedrozo requested a review from a team as a code owner July 23, 2026 07:57
@manupedrozo
manupedrozo requested review from blva and himanshusinghs and removed request for a team and himanshusinghs July 23, 2026 07:57
@manupedrozo
manupedrozo merged commit 345fdf4 into main Jul 24, 2026
40 of 42 checks passed
@manupedrozo
manupedrozo deleted the CLOUDP-407393-create-cluster-cmk-support branch July 24, 2026 09:10
Comment on lines +445 to +458
prompt: `Create a cluster named "${CLUSTER_NAME}" in project "${PROJECT_ID}" on AWS in US_EAST_1 and enable KMS via AWS`,
mockedTools: {
...mockListProjects,
"atlas-create-cluster": mockCreateClusterResponse({
projectId: PROJECT_ID,
clusterName: CLUSTER_NAME,
provider: "AWS",
region: "US_EAST_1",
}),
},
expectedToolCalls: [
...optionalListProjects,
{
toolName: "atlas-create-cluster",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these test cases cover the 3 cases specified in the TD? (specifically the no preference/unset case)

  • An explicitly requested CMK provider is passed to the tool.
  • An explicit ask not to use a CMK results in NONE.
    - Prompts that do not express a CMK preference leave the input unset.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is covered by existing tests, which do not mention encryption at rest.
If any value is passed for encryptionAtRestProvider in those, the expected call no longer matches and accuracy drops.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-title-validation Add this label to disable the title check for this PR. type: feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants