Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(core): add optional name to kas registry CRUD commands #429

Merged
merged 8 commits into from
Nov 20, 2024

Conversation

jakedoublev
Copy link
Contributor

No description provided.

@jakedoublev jakedoublev requested a review from a team as a code owner November 19, 2024 19:47
Copy link
Member

@damorris25 damorris25 left a comment

Choose a reason for hiding this comment

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

@jakedoublev do you mind adding a couple of negative tests in addition to the positive tests?
Perhaps a few tests that:

  • an invalid name? Do we allow non-ascii characters for example?
  • a name that is too long? (is there a limit)

@jakedoublev
Copy link
Contributor Author

jakedoublev commented Nov 19, 2024

@jakedoublev do you mind adding a couple of negative tests in addition to the positive tests? Perhaps a few tests that:

  • an invalid name? Do we allow non-ascii characters for example?
  • a name that is too long? (is there a limit)

@damorris25 Sure thing. The negative paths around name validity are enforced by protos and unit tested but I don't mind if we end to end test them as well with this CLI as the primary client engaging the APIs.

There's also a separate PR in flight to provide more helpful/clear validation to the key itself: #428

@jakedoublev jakedoublev enabled auto-merge (squash) November 20, 2024 15:47
Copy link
Contributor

@ryanulit ryanulit left a comment

Choose a reason for hiding this comment

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

Looks good to me, just one question. I noticed the key type is being removed, do you still need that or is it part of the GetPublicKey().String() output now?

@jakedoublev jakedoublev merged commit f675d86 into main Nov 20, 2024
7 checks passed
@jakedoublev jakedoublev deleted the feat/kasr-name branch November 20, 2024 15:48
@jakedoublev
Copy link
Contributor Author

Looks good to me, just one question. I noticed the key type is being removed, do you still need that or is it part of the GetPublicKey().String() output now?

@ryanulit That's exactly right. If we don't marshal the key to JSON first and convert the proto type to a string instead, we get the key type in the table output, so we can remove the extra detection/variable. We were also inconsistent between CRUD commands before and are now consistent.

jakedoublev pushed a commit that referenced this pull request Nov 20, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.16.0](v0.15.0...v0.16.0)
(2024-11-20)


### Features

* assertion verification disable
([#419](#419))
([acf5702](acf5702))
* **core:** add `subject-mappings match` to CLI
([#413](#413))
([bc56c19](bc56c19))
* **core:** add optional name to kas registry CRUD commands
([#429](#429))
([f675d86](f675d86))
* **core:** adds assertions to encrypt subcommand
([#408](#408))
([8f0e906](8f0e906))
* **core:** adds storeFile to save encrypted profiles to disk and
updates auth to propagate tlsNoVerify
([#420](#420))
([f709e01](f709e01))
* refactor encrypt and decrypt + CLI examples
([#418](#418))
([e681823](e681823))
* support --with-access-token for auth
([#409](#409))
([856efa4](856efa4))


### Bug Fixes

* **core:** dev selectors employ flattening from platform instead of jq
([#411](#411))
([57966ff](57966ff))
* **core:** improve readability of TDF methods
([#424](#424))
([a88d386](a88d386))
* **core:** remove trailing slashes on host/platformEndpoint
([#415](#415))
([2ffd3c7](2ffd3c7)),
closes [#414](#414)
* **core:** revert profiles file system storage last commit
([#427](#427))
([79f2079](79f2079))
* updates sdk to 0.3.19 with GetTdfType fixes
([#425](#425))
([0a9adfe](0a9adfe))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: opentdf-automation[bot] <149537512+opentdf-automation[bot]@users.noreply.github.com>
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