Skip to content

client: support cmk operations#433

Open
hnousiainen wants to merge 1 commit intoaiven:mainfrom
hnousiainen:htn_cmk_initial_ops
Open

client: support cmk operations#433
hnousiainen wants to merge 1 commit intoaiven:mainfrom
hnousiainen:htn_cmk_initial_ops

Conversation

@hnousiainen
Copy link
Copy Markdown
Contributor

Implement initial support for CMK operations.

@hnousiainen hnousiainen requested review from a team as code owners November 26, 2025 07:41
@hnousiainen hnousiainen requested a review from Prime541 November 26, 2025 07:41
Copy link
Copy Markdown

@glenn-mcallister-aiven glenn-mcallister-aiven left a comment

Choose a reason for hiding this comment

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

I have to block this, for a couple of reason:

  1. Most of these commands are using optional style arguments (i.e., --cmk-id) for required arguments. That's a major UX no-no.
  2. WAY MORE significantly, the current implementation is intended for xxxxxxx only, to the point where
    1. we are hiding access to the the API behind an ACL,
    2. we aren't documenting the API in our public API docs,
    3. xxxxxx does changes only through TF, meaning they need API access only.

Once these changes get published, customers are going to see that there are "customer managed keys" commands, which is 100% what we don't want currently.

@hnousiainen hnousiainen force-pushed the htn_cmk_initial_ops branch 2 times, most recently from 4fdb8fa to bb5cd8e Compare February 4, 2026 15:06
@hnousiainen hnousiainen dismissed glenn-mcallister-aiven’s stale review February 4, 2026 15:08

We're getting ready to introduce this functionality at large, so I'm dismissing the blocker on customer concerns. There's nothing secret in us pursuing this functionality.

Copy link
Copy Markdown
Contributor

@VadimPushtaev VadimPushtaev left a comment

Choose a reason for hiding this comment

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

Some typos, but generally fine. --cmk-id being required pattern is a pretty common pattern for aiven-client anyway.

Comment thread aiven/client/cli.py
@arg("--default-cmk", help="Mark CMK as default for all new services", choices=["true", "false"])
@arg.json
def project__cmks__update(self) -> None:
"""Define a project customer managed key (CMK)"""
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copy-pasted message, probably should be "Change", not "Define".

Comment thread aiven/client/cli.py
@arg("--cmk-id", help="CMK Identifier", required=True)
@arg.json
def project__cmks__get(self) -> None:
"""Get details on a customer managed keys (CMKs)"""
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

*key

Comment thread aiven/client/cli.py
@arg("--cmk-id", help="CMK Identifier", required=True)
@arg.json
def project__cmks__delete(self) -> None:
"""Delete a customer managed keys (CMKs)"""
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

  • keys

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants