-
Notifications
You must be signed in to change notification settings - Fork 23
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
chore(main): release access 4.0.0 #130
Merged
alanshaw
merged 1 commit into
main
from
release-please--branches--main--components--access
Nov 1, 2022
Merged
chore(main): release access 4.0.0 #130
alanshaw
merged 1 commit into
main
from
release-please--branches--main--components--access
Nov 1, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deploying with
|
Latest commit: |
89fd9ea
|
Status: | ✅ Deploy successful! |
Preview URL: | https://15664438.ucan-protocol.pages.dev |
Branch Preview URL: | https://release-please--branches--ma-sudd.ucan-protocol.pages.dev |
31a2ebf
to
bfacf74
Compare
bfacf74
to
89fd9ea
Compare
alanshaw
approved these changes
Nov 1, 2022
gobengo
pushed a commit
that referenced
this pull request
Apr 11, 2023
🤖 I have created a release *beep* *boop* --- ## [4.0.0](access-v3.1.2...access-v4.0.0) (2022-11-01) ### ⚠ BREAKING CHANGES * Remove 0.8 caps and add account delegation to the service (#123) ### Features * add cancel create account ([#132](#132)) ([0336116](0336116)) * Remove 0.8 caps and add account delegation to the service ([#123](#123)) ([c3c58b9](c3c58b9)), closes [#117](#117) [#121](#121) ### Bug Fixes * throw error or return value ([#131](#131)) ([c9abfb9](c9abfb9)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
fforbeck
added a commit
that referenced
this pull request
Sep 20, 2024
# Add `shareSpace()` Method to Allow Sharing Spaces with Other Accounts ## Summary This PR introduces a new `shareSpace()` method that allows users to delegate access to an existing space with another Storacha account via email. This feature enhances collaboration by enabling multiple accounts to share access to a space, making data sharing more flexible. By default, the following capabilities/permissions are set: - space/* - for managing space metadata - store/* - for managing stores - upload/*- for registering uploads - access/* - for re-delegating access to other devices - filecoin/* - for submitting to the filecoin pipeline - usage/* - for querying usage ## Changes ### New Feature: **Space Sharing** - **Added `shareSpace()` Method**: - The `shareSpace()` method allows users to share an existing space with another Storacha account by delegating access to the specified email address. - The method takes in the following options: - `space`: The space to be shared, identified by its DID. - `delegateEmail`: The email address of the account to share the space with. - The sharing process involves: 1. **Creating a delegation for the delegate account**: This ensures that the delegate has access to the space. 2. **Delegating access**: Space access is delegated to the provided email account, allowing the delegate to manage and access the space. - If the sharing process fails, the method throws an error detailing the issue. ## How to Test 1. Run the following commands: ```bash npm run build && npm run test ``` 2. Ensure all existing tests pass. 3. Verify that the new test cases for the `shareSpace()` method function correctly. ## Related Issues - [Issue #130](storacha/project-tracking#130): Enable space sharing between accounts. ## Additional Notes This implementation opens the door for future enhancements, such as specifying different permission levels when sharing spaces.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
4.0.0 (2022-11-01)
⚠ BREAKING CHANGES
Features
Bug Fixes
This PR was generated with Release Please. See documentation.