* Added new report card and FeatureFlag for MemberAccessReport
* Add new "isEnterpriseOrgGuard"
* Add member access icon
* Show upgrade organization dialog for enterprise on member access report click
* verify member access featureflag on enterprise org guard
* add comment with TODO information for follow up task
* Initial member access report component
* Improved readability, removed path to wrong component and refactored buildReports to use the productType
* finished MemberAccessReport layout and added temporary service to provide mock data
* Moved member-access-report files to bitwarden_license/
Removed unnecessary files
* Added new tools path on bitwarden_license to the CODEOWNERS file
* added member access description to the messages.json
* layout changes to member access report
* Created new reports-routing under bitwarden_license
Moved member-access-report files to corresponding subfolder
* Added search logic
* Removed routing from member-access-report BL component on OSS.
Added member-access-report navigation to organizations-routing on BL
* removed unnecessary ng-container
* Added OrganizationPermissionsGuard and canAccessReports validation to member-access-report navigation
* replaced deprecated search code with searchControl
* Address PR feedback
* removed unnecessary canAccessReports method
Factor general integration logic out of the forwarder code.
- Integration metadata - information generalized across any integration
- Rpc mechanism - first step towards applying policy to integrations is abstracting their service calls (e.g. static baseUrl)
Email forwarder integrations embedded this metadata. It was extracted to begin the process of making integrations compatible with meta-systems like policy.
This PR consists mostly of interfaces, which are not particularly useful on their own. Examples on how they're used can be found in the readme.
* Updated codeowners for new design system team.
* Moved Angular and Bootstrap dependencies
* Moved additional dependencies.
* Updated ownership
Co-authored-by: Will Martin <contact@willmartian.com>
---------
Co-authored-by: Will Martin <contact@willmartian.com>
* Update the build job to use `bit` artifacts for stores
* Update the CLI's license in `package.json` for the NPM store
* Add license configuration to `snapcraft.yaml`
* Add setuptools to mac pipeline
Mac runners have progressed above python 3.12, which removed `distutils`. We need to ensure it's installed for node-gyp compilations by installing the setuptools package.
* Add missed mac build
* [deps] Platform: Update argon2 to v0.40.1
* Update inclusion in context isolation
* Ensure node-gyp available for mac builds
Mac runners seem to have progressed above python 3.12, which removed `distutils`. We need to ensure it's installed for node-gyp compilations.
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Matt Gibson <mgibson@bitwarden.com>
* include check-run in workflows where secrets are used
* revert changes in build-cli workflow and add check-run to codecov
* assert token permissions
* include required permissions
* re-arrange permissions in alphabetical order
---------
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
* include check-run in workflows where secrets are used
* revert changes in build-cli workflow and add check-run to codecov
* assert token permissions
---------
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
Utilizing resources based on thread availability improves performance vs fixed threading.
The linked issue for CI crashes has not been closed. Once this is solves, `runInBand` may improves performance in CI.
* Update .nvmrc from v18 to v20
* Update engines setting node 18->20 and npm 9->10
* Use yao-pkg/pkg instead of vercel/pkg
---------
Co-authored-by: Daniel James Smith <djsmith85@users.noreply.github.com>
* Create the send-ui library package
Create folder
Create package.json
Create jest config
Create tsconfig and tsconfig.spec.json
Create README
Add empty barrel file for exporting future members
* Register @bitwarden/send-ui with all clients and libs
* Register with eslint
* Fix linting issue with README
---------
Co-authored-by: Daniel James Smith <djsmith85@users.noreply.github.com>
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Incorporate build workflow for the Chrome manifest v3 beta
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Ensure we can have a valid version number based on the github run id
* [PM-7663] Ensure we can have a valid version number based on the github run id
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting a typo
* Fix Duplicate `process.env
* Learn how to use
---------
Co-authored-by: Justin Baur <19896123+justindbaur@users.noreply.github.com>
* Initial run to see what data I can access
* Update to use JQ
* Use dev action
* Implement artifact build sha
- Moved notify job to happen post artifact check
- Removed git sha job
- Updated jobs to use real artifact sha
* Update .github/workflows/deploy-web.yml
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
* Handle web build triggers
- Update GH environment with commit as well
---------
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
* [PM-7527] Get MV3 build artifacts in main branch with clear messaging that that the build is not to be released
* [PM-7527] Add `Build Manifest v3` build step to the build-browser.yml Github action
* [PM-7527] Get MV3 build artifacts in main branch with clear messaging that that the build is not to be released
* Update .github/workflows/build-browser.yml
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
---------
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
* implementing the clients changes
* resolve pr comments on message.json
* moved the method to billing-api.service
* move the request and response files to billing folder
* remove the adding existing orgs
* resolve the routing issue
* resolving the pr comments
* code owner changes
* fix the assignedseat
* resolve the warning message
* resolve the error on update
* passing the right id
* resolve the unassign value
* removed unused logservice
* Adding the loader on submit button
* DEVOPS-1843 REFACTOR: Trigger web vault deploy step to send the build-web run-id to deploy-web workflow
* DEVOPS-1843 ADD: build-web-run-id input to deploy-web workflow to download specific run_id artifact
* DEVOPS-1843 FIX: build-web-run-id input in build-web workflow
* DEVOPS-1843 REFACTOR: build-web-run-id parameter type to number
* DEVOPS-1843 ADD: build-web-run-id input to deploy-web workflow to workflow_dispatch
* DEVOPS-1843 FIX: build-web-run-id type in deploy-web.yml
* DEVOPS-1843 REFACTOR: web vault deploy action to use GitHub Run ID
* DEVOPS-1843 REFACTOR: cloud asset download steps in deploy-web.yml
* DEVOPS-1843 REFACTOR: description for build-web workflow Run ID
Co-authored-by: MtnBurrit0 <77340197+mimartin12@users.noreply.github.com>
---------
Co-authored-by: MtnBurrit0 <77340197+mimartin12@users.noreply.github.com>
