Add support for Global API Key in Cli

[Taohao Wang (taohaowang)]

Release Notes

New Features

• Add “global” option for confluent api-key [create | list] --resource

Checklist

• I have successfully built and used a custom CLI binary, without linter issues from this PR.
• I have clearly specified in the What section below whether this PR applies to Confluent Cloud, Confluent Platform, or both.
• I have verified this PR in Confluent Cloud pre-prod or production environment, if applicable.
• I have verified this PR in Confluent Platform on-premises environment, if applicable.
• I have attached manual CLI verification results or screenshots in the Test & Review section below.
• I have added appropriate CLI integration or unit tests for any new or updated commands and functionality.
• I confirm that this PR introduces no breaking changes or backward compatibility issues.
• I have indicated the potential customer impact if something goes wrong in the Blast Radius section below.
• I have put checkmarks below confirming that the feature associated with this PR is enabled in:
  • Confluent Cloud prod
  • Confluent Cloud stag
  • Confluent Platform
  • Check this box if the feature is enabled for certain organizations only

What

Confluent Cloud
Support UAK - Global API key creation

Blast Radius

Low blast radius - only impact UAK - global API key (which is a new feature)
This feature is not yet enabled in prod.

References

https://confluentinc.atlassian.net/browse/IDENTITY-5922

Test & Review

./dist/confluent_darwin_arm64_v8.0/confluent api-key create --resource global
It may take a couple of minutes for the API key to be ready.
Save the API key and secret. The secret is not retrievable later.
+------------+------------------------------------------------------------------+
| API Key    | YEKD6II4MMX4MGKH                                                 |
| API Secret | <redacted> |
+------------+------------------------------------------------------------------+

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[Copilot]

Pull request overview

This PR adds support for creating Global API keys in the Confluent CLI, extending the existing API key management functionality to support a new resource type alongside Cloud, Flink, and Tableflow API keys.

Changes:

• Added "global" as a new resource type constant and integrated it throughout the API key lifecycle (create, list, lookup)
• Updated command documentation and help text to reference Global API keys
• Added test coverage for the new Global API key resource type

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
pkg/resource/resource.go	Added Global constant and updated LookupType function to recognize "global" as a valid resource type
internal/api-key/command_test.go	Added test case for Global API key resource type resolution
internal/api-key/command_list.go	Updated list and getResourceId functions to handle Global resource type
internal/api-key/command_create.go	Added example for Global API key creation and case handling in create function
internal/api-key/command.go	Updated help text, autocomplete suggestions, and resource type resolution to include Global API keys

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqube-confluent]

Quality Gate passed

Issues
1 New issue
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
90.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[Daniel Ayaz (danielayaz)]

Looks good to me

[Channing Dong (channingdong)]

Can we create the dedicated integration test in api_key_test.go to verify the global API key?

Something like:

{args: "api-key create --description human-output --resource global", fixture: "api-key/xxx.golden"},

[Channing Dong (channingdong)]

Also, for the Release Note section, could you please revert it to its original format? The CLI release pipeline needs its original format to extract the release notes:

Breaking Changes
- PLACEHOLDER

New Features
- PLACEHOLDER

Bug Fixes
- PLACEHOLDER

[sonarqube-confluent]

Quality Gate passed

Issues
1 New issue
1 Fixed issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube