Skip to content
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

fix(space-creator): check provision result before proceeding #119

Merged
merged 3 commits into from
Sep 4, 2024

Conversation

fforbeck
Copy link
Member

@fforbeck fforbeck commented Sep 4, 2024

Issue

If the NEXT_PUBLIC_W3UP_PROVIDER environment variable is not set, the app will use did:web:web3.storage as the default storage provider. That works well if we are pointing to Prod environment (https://up.web3.storage), however, if we use the Staging environment (https://staging.up.web3.storage) it will fail to provision the space because the default provider is invalid for Staging.

Fix

  • Verify if the Space Provisioning result contains an error. If so, throw the error to prevent the user from continuing the flow and attempting to upload files.
  • Updated Docs and sample Env Vars.

Copy link
Contributor

github-actions bot commented Sep 4, 2024

Website preview 🔗✨

build log

README.md Outdated Show resolved Hide resolved
src/components/SpaceCreator.tsx Outdated Show resolved Hide resolved
fforbeck and others added 2 commits September 4, 2024 11:15
Copy link
Member

@alanshaw alanshaw left a comment

Choose a reason for hiding this comment

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

LGTM

@fforbeck fforbeck merged commit c15c379 into main Sep 4, 2024
5 checks passed
@fforbeck fforbeck deleted the fix-provider-error branch September 4, 2024 14:28
fforbeck added a commit that referenced this pull request Sep 17, 2024
# Issue
If the `NEXT_PUBLIC_W3UP_PROVIDER` environment variable is not set, the
app will use `did:web:web3.storage` as the default storage provider.
That works well if we are pointing to Prod environment
(https://up.web3.storage), however, if we use the Staging environment
(https://staging.up.web3.storage) it will fail to provision the space
because the default provider is invalid for Staging.

# Fix 
- Verify if the Space Provisioning result contains an error. If so,
throw the error to prevent the user from continuing the flow and
attempting to upload files.
- Updated Docs and sample Env Vars.

---------

Co-authored-by: Alan Shaw <[email protected]>
hannahhoward added a commit that referenced this pull request Sep 20, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.10.0](w3console-v1.9.1...w3console-v1.10.0)
(2024-09-04)


### Features

* **copy:** Add missing comma
([#115](#115))
([5f3cf7b](5f3cf7b))


### Bug Fixes

* check ref
([f406ac9](f406ac9))
* quotes
([bcf209b](bcf209b))
* **space-creator:** check provision result before proceeding
([#119](#119))
([c15c379](c15c379))
* use correct branch name
([f81e090](f81e090))
* use main branch
([698974b](698974b))


### Other Changes

* add storacha deploy action
([39345e6](39345e6))
* Set `packageManager`
([#117](#117))
([5f135df](5f135df))
* update deploy name
([f7c1340](f7c1340))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: Alan Shaw <[email protected]>
Co-authored-by: Petra Jaros <[email protected]>
Co-authored-by: Felipe Forbeck <[email protected]>
Co-authored-by: Hannah Howard <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
hannahhoward pushed a commit that referenced this pull request Sep 20, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.10.0](w3console-v1.9.1...w3console-v1.10.0)
(2024-09-20)


### Features

* change email
([7c7beb7](7c7beb7))
* **copy:** Add missing comma
([#115](#115))
([97f1ac3](97f1ac3))
* Improved layout styling, and other tales
([#114](#114))
([d0a2208](d0a2208))
* more styles
([d4e8efa](d4e8efa))
* styles for upload page
([6c54798](6c54798))
* trigger deploy
([a8f1089](a8f1089))
* wording
([ffe9b1b](ffe9b1b))


### Bug Fixes

* apostrophe
([681b9b8](681b9b8))
* check ref
([f406ac9](f406ac9))
* deploy-storacha.yml needs to use the new main branch
([#122](#122))
([65644c8](65644c8))
* deploy.yml needs to use the old-main branch
([#120](#120))
([713af05](713af05))
* quotes
([bcf209b](bcf209b))
* **space-creator:** check provision result before proceeding
([#119](#119))
([5ea5940](5ea5940))
* use correct branch name
([f81e090](f81e090))
* use main branch
([698974b](698974b))


### Other Changes

* add storacha deploy action
([39345e6](39345e6))
* Set `packageManager`
([#117](#117))
([c9436fc](c9436fc))
* update deploy name
([f7c1340](f7c1340))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

2 participants