-
Notifications
You must be signed in to change notification settings - Fork 94
Add schema name step to Connectors init workflow #2647
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
Merged
Merged
Conversation
This file contains hidden or 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
|
da44f4f
to
37bfaf2
Compare
37bfaf2
to
8a0d598
Compare
8a0d598
to
d187ecd
Compare
tayrrible
approved these changes
Jul 9, 2025
alyssahursh
added a commit
that referenced
this pull request
Jul 10, 2025
This PR removes the use case guard clause in the schema name prompt. When the original work to add the schema name prompt was written (#2647), I made the incorrect assumption that we would only want to prompt for a schema name in the Connector use case. My changes were tested with and intended to work with this PR: apollographql/rover-init-starters#51 Because this work was done as part of the 2025 Hackathon project, a different commit to `rover-init-starters` was merged instead: apollographql/rover-init-starters#52 This version assumes that the schema prompt will happen regardless of project type. This PR adapts 2467 to work with the work that was merged in `rover-init-starters` ### Testing 1. Ran `cargo build` to build these `rover` changes 1. Aliased `cargo rover` to `localrover` with `alias localrover='cargo run --manifest-path=/Users/alyssahursh/code/rover/Cargo.toml --bin rover --'` 1. Created new empty test directory 1. Ran `localrover init` 1. Verified that connectors init workflow prompted for a schema name 1. Verified `supergraph.yaml` file was created using the newly provided schema name ``` graph_ref: my-api-m55izjn@current subgraphs: main-schema-name: routing_url: http://localhost:4001 schema: file: schema.graphql ```
Merged
DaleSeo
added a commit
that referenced
this pull request
Jul 30, 2025
# [0.35.0] - 2025-07-30 ## ❗ BREAKING ❗ - **use config file for MCP server - @nicholascioli PR #2665** ## 🚀 Features - **Update MCP options for rover dev - @DaleSeo PR #2661** - **Add schema name step to Connectors init workflow - @alyssahursh PR #2647** - **Allow running rover dev without --supergraph-config if you have a rover.yaml in the current directory - @dylan-apollo PR #2650** - **Updating output for init & renaming generated "supergraph.yaml" -> "rover.yaml" - @tayrrible PR #2651** - **Adds support for .env file for use with rover dev - @DMallare PR #2646** - **Add graph_ref to and remove federation_version from subgraph.yaml - @alyssahursh PR #2649** - **Hackathon improvements to supergraph.yaml - @dylan-apollo PR #2648** - **Adding link to studio for graph & showing each step in creation process via spinners - @tayrrible PR #2657** - **Generates .env file with rover init - @DMallare PR #2652** - **Remove use case guard clause in schema name prompt - @alyssahursh PR #2655** - **Set APOLLO_GRAPH_REF from rover.yaml's graph_ref - @dylan-apollo PR #2653** - **Adding apollo.config.yaml file for connectors projects - @tayrrible PR #2658** - **add a note about the need for APOLLO_KEY and APOLLO_GRAPH_REF when using router features or connect - @the-gigi-apollo PR #2677** - **Update Studio Client after loading .env in rover dev - @dylan-apollo PR #2654** - **Exposing org selector for all runs of init and changing prompt order - @tayrrible PR #2656** ## 🛠 Maintenance - **upgrade schemars and apollo-federation-types - @DaleSeo PR #2676**
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.
This PR adds a schema naming step to the Connectors init workflow. Previously, running
rover init
for a Connectors project would generate a boilerplate schema namedproducts
. Not all customers have the concept of "products," and trying to change the name of the subgraph causes unnecessary friction. This change allows users to provide their own schema name, which is then populated into thesupergraph.yaml
file.This PR is intended to be deployed with compensating changes in
rover-init-starters
: apollographql/rover-init-starters#51 This change should be deployed before those changes, as the reverse order will causerover init
to panic when it encounters a root-level.graphql
file namedschema
.Testing
products.graphql
toschema.graphql
inrover-init-starters
rover-init-starters
changes toorigin/schema-rename
rover
to pull templates fromschema-rename
branch by modifying[repo_ref](https://github.com/apollographql/rover/blob/dd29b918fc84f862ab68c300b39d7f336d93f8ea/src/command/init/transitions.rs#L242)
locallycargo build
to build theserover
changescargo rover
tolocalrover
withalias localrover='cargo run --manifest-path=/Users/alyssahursh/code/rover/Cargo.toml --bin rover --'
localrover init
supergraph.yaml
file was created using the newly provided schema nameThis PR is part of the 2025 Hackathon.