Skip to content

Conversation

@arinda-arif
Copy link
Contributor

No description provided.

@sbchaos sbchaos force-pushed the optimus-secret-management branch 2 times, most recently from 27b7479 to 9788779 Compare January 3, 2022 10:24
@sbchaos sbchaos force-pushed the optimus-secret-management branch 2 times, most recently from 422ffc7 to efd2669 Compare January 4, 2022 09:55
@sbchaos sbchaos force-pushed the optimus-secret-management branch from efd2669 to ed15955 Compare January 5, 2022 04:16
Comment on lines +587 to +588
bool success = 1;
string message = 2;
Copy link
Member

Choose a reason for hiding this comment

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

How are we using these? I don't think we need a success flag here?

Copy link
Contributor

Choose a reason for hiding this comment

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

Sure, will remove success flag from the proto in next PR.

@sbchaos sbchaos merged commit 1ac8ad9 into main Jan 25, 2022
@sbchaos sbchaos deleted the optimus-secret-management branch January 25, 2022 08:00
sbchaos added a commit that referenced this pull request Feb 14, 2022
* feat(optimus): add namespace name to RegisterSecretRequest (#83)

* feat(optimus): add namespace name to RegisterSecretRequest

* feat(optimus): add option for update_only in RegisterSecretRequest

* feat(optimus): add updateSecret api

Co-authored-by: Sandeep Bhardwaj <[email protected]>

* feat(optimus): add listSecrets api, remove unused field from secrets responses

Co-authored-by: Arinda Arif <[email protected]>
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.

4 participants