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(cli): Add deprecation notice for edgio deployment #10551

Merged
merged 3 commits into from
May 11, 2024

Conversation

Josh-Walker-GM
Copy link
Collaborator

Changes

  1. Adds a deprecation notice to the cli for the setup and deploy commands for the edgio deployment provider.
  2. Adds a deprecation notice to the edgio deployment documentation.

Notes

  1. On the documentation change: I didn't explicitly create a forum post to provide insight into this decision instead I simply asked anyone who has input to do so.
  2. I used both the yargs deprecated config and also used the same style of adding DEPRECATED to the setup command description that had been used for the serverless deploy deprecation notice.

@Josh-Walker-GM Josh-Walker-GM added the release:fix This PR is a fix label May 8, 2024
@Josh-Walker-GM Josh-Walker-GM added this to the next-release milestone May 8, 2024
@Josh-Walker-GM Josh-Walker-GM self-assigned this May 8, 2024
@Josh-Walker-GM Josh-Walker-GM merged commit 747ce41 into main May 11, 2024
46 checks passed
@Josh-Walker-GM Josh-Walker-GM deleted the jgmw/deprecate-edgio-deploy-provider branch May 11, 2024 13:23
@thedavidprice
Copy link
Contributor

Thank you for doing this 🚀

@thedavidprice
Copy link
Contributor

@Josh-Walker-GM one reminder and future to-do: Before we chose to fully remove this in the next major, we should communicate with the Edg.io team to see if they would like to pick-up support. If they do, we could make a handoff so users have an alternative. Most of all, I just don't want them to be surprised.

For those curious as to why this deprecation is being added:

  • Edg.io packages for Redwood deployment are no longer working
  • We noticed this after v7; effectively, this deploy provider has not been working
  • usage for this deploy provider has been minimal, which is why no one caught the deployment issue

dac09 added a commit that referenced this pull request May 15, 2024
…uth-store

* 'main' of github.com:redwoodjs/redwood:
  chore(router): Add more code comments to analyzeRoutes (#10569)
  RSC: No need to use memo or useMemo in the server router (#10568)
  RSC: getViteConfig in rscWorker (#10567)
  Split RSC and RSA handling in rscWorker (#10565)
  RSC: Extract the fetchRSC function (#10564)
  RSC: Fix TODO regarding SSR in client.ts (#10562)
  Docs: QoL Updates to Contributing.md (#10561)
  Added warning note to not add WebAuthn (#10231)
  fix(rsc): Load all css links to support css with rsc (#10544)
  fix(cli): Add deprecation notice for edgio deployment (#10551)
  Define `process.env.NODE_ENV` in build process. (#10553)
  chore(docs): Update dbAuth and Supabase middleware READMEs (#10552)
  chore(deps): Upgrade React 19 to beta 20240508 (#10560)
  Revert "chore(deps): React beta 20240508 (#10558)" (#10559)
  chore(deps): React beta 20240508 (#10558)
  fix(functions): Fix context variable warning/error (#10556)
  fix(functions): Mock context in function test template (#10555)
  chore(middleware): Format code and comments and fix comment grammar (#10554)
Josh-Walker-GM added a commit that referenced this pull request May 15, 2024
**Changes**
1. Adds a deprecation notice to the cli for the setup and deploy
commands for the edgio deployment provider.
2. Adds a deprecation notice to the edgio deployment documentation. 

**Notes**
1. On the documentation change: I didn't explicitly create a forum post
to provide insight into this decision instead I simply asked anyone who
has input to do so.
2. I used both the yargs `deprecated` config and also used the same
style of adding `DEPRECATED` to the setup command description that had
been used for the serverless deploy deprecation notice.
@Josh-Walker-GM Josh-Walker-GM modified the milestones: next-release, v7.6.0 May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:fix This PR is a fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants