- Add empty permission set at workflow level to remove default GITHUB_TOKEN permissions
- Add empty permission set to setup job as it only runs bash commands
- Add contents:write to GitHub App tokens in bump_version and cut_branch jobs for git operations
- Add empty permission set to move_edd_db_scripts job as called workflow declares its own permissions
- Remove secrets:inherit as called workflow accesses Azure secrets directly
* Validate any SQL migration scripts are the most recent
* Make string checks more robust
* Clarify script location
* Remove need given the additional validations that are immediately valuable
* Allow past incorrectly-named migrations but now enforce
* Centralize validation logic to PowerShell script
Adds a Rust SDK for performing seed related cryptograhic operations. It depends on internal portions of our Rust SDK. Primarily parts of the bitwarden-crypto crate.
Create new action for Claude Code Review of Vault Team Code. Worked to align what we have here with the initial `mcp-server` repo's code review action.
* Remove external loadImpact option that is being replaced by DataDog
* Add load test workflow
Keep otel encrypted, but skip verification
Go back to what was working from Billing-Relay
Tune test configuration based on last test output.
Tune config loadtest
Tune tests a bit more by removing preAllocatedVUs
Revert "Tune tests a bit more by removing preAllocatedVUs"
This reverts commit ab1d170e7a3a6b4296f2c44ed741656a75979c80.
Revert "Tune config loadtest"
This reverts commit 5bbd551421658e8eb0e2651fb1e005c7f1d52c99.
Tune config.js by reducing the amount of pAV
Revert "Tune config.js by reducing the amount of pAV"
This reverts commit 1e238d335c27ebf46992541ca3733178e165b3aa.
Drop MaxVUs
* Update .github/workflows/load-test.yml
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
* Fix newline at end of load-test.yml file
* Fix github PR accepted code suggestion
---------
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
* Move PushType to Platform Folder
- Move the PushType next to the rest of push notification code
- Specifically exclude it from needing Platform code review
- Add tests establishing rules Platform has for usage of this enum, making it safe to have no owner
* Move NotificationHub code into Platform/Push directory
* Update NotificationHub namespace imports
* Add attribute for storing push type metadata
* Rename Push Engines to have PushEngine suffix
* Move Push Registration items to their own directory
* Push code move
* Add expected usage comment
* Add Push feature registration method
- Make method able to be called multipes times with no ill effects
* Add Push Registration service entrypoint and tests
* Use new service entrypoints
* Test changes
