Add migration guide from the Apollo CLI -> Rover #425
Conversation
| @@ -1,14 +1,18 @@ | |||
| { | |||
There was a problem hiding this comment.
I copied these changes directly from apollo-server
JakeDawkins
force-pushed
the
jake/migration
branch
from
926b777
to
271afde
Compare
There was a problem hiding this comment.
this looks great @JakeDawkins - thanks a bunch for putting this together
docs/source/migration.md
Outdated
|
|
||
| ## Configuring | ||
|
|
||
| Rover's approach to [configuration](./configuring) is much more granular and less abstracted than the Apollo CLI. Most configuration options in Rover are configured as flags on a command, rather than items in a config file. The only config files that Rover uses are hidden config files created by the `config auth` command and another as input to [`supergraph compose`](./supergraphs#configuration). |
There was a problem hiding this comment.
Perhaps it's worth noting what the old config format looks like/the info it contains and then map each of those values to how you'd configure it in rover?
There was a problem hiding this comment.
I'll see what I can do for that. I had the same thought, but there's a bunch of edge cases with the old config. I think I can figure something out though 😄
| @@ -17,17 +17,13 @@ module.exports = { | |||
| 'getting-started', | |||
| 'configuring', | |||
| 'ci-cd', | |||
| 'essentials', | |||
There was a problem hiding this comment.
should we consider adding a redirect to conventions from essentials?
There was a problem hiding this comment.
we could, but I don't think it's stricly necessary. If we were in GA, I'd say probably
There was a problem hiding this comment.
Uh oh looks like this was necessary! I'll add momentarily
Resolves #284