-
Notifications
You must be signed in to change notification settings - Fork 50
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
[SM-1153] Part 1 Secrets sync | Generate API bindings #674
Conversation
The command I reverted the changes for the I did notice the replacements had an extra dependency |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #674 +/- ##
=======================================
Coverage 58.77% 58.77%
=======================================
Files 177 177
Lines 11501 11501
=======================================
Hits 6760 6760
Misses 4741 4741 ☔ View full report in Codecov by Sentry. |
Yeah for the moment the Cargo.toml changes need to be reverted manually. Thankfully those two files don't need to change very often outside of version bumps. The generated bindings aren't using the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought... When this is ready we may want to re-run ./support/build-api.sh
to verify these changes, and check if there are new changes we want to include or updates to non-SM items we need to include.
No New Or Fixed Issues Found |
Went ahead and regenerated the API bindings off of main, since this should be ready to go now. Most of the SM additional changes are coming from recent access policy endpoint updates. Since we don't use those endpoints in the SDK should be fine to bring in here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Bindings match with a local build
## Type of change <!-- (mark with an `X`) --> ``` - [ ] Bug fix - [X] New feature development - [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc) - [ ] Build/deploy pipeline (DevOps) - [ ] Other ``` ## Objective <!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding--> The purpose of this PR is to expose the ability to preform secrets syncs via the Secrets Manager SDK. Requires API bindings in #674 This should not be merged into main prior to: - The server PR bitwarden/server#3906 being merged and released - The API bindings PR #674 being merged into main ## Code changes <!--Explain the changes you've made to each file or major component. This should help the reviewer understand your changes--> <!--Also refer to any related changes or PRs in other repositories--> - **crates/bitwarden/src/secrets_manager/client_secrets.rs:** Add the `sync` method to the client secrets. - **crates/bitwarden/src/secrets_manager/secrets/mod.rs:** Expose `sync` `SecretsSyncRequest`, and `SecretsSyncResponse` - **crates/bitwarden/src/secrets_manager/secrets/sync.rs:** Implement `sync` `SecretsSyncRequest`, and `SecretsSyncResponse` ## Before you submit - Please add **unit tests** where it makes sense to do so
Type of change
Objective
Expose the new secrets sync endpoint.
Server PR bitwarden/server#3906
Code changes
ran the command
./support/build-api.sh
Before you submit