v0.8.0 installed from npm broken due to superfluous output on STDOUT

[kpachbiu88]

In Rover version 0.8.0 add extra message in the schema and breaks it

Command: rover subgraph introspect https://api-test.test.com/main/graphql > test.graphql
Result test.graphql:

If you would like to disable Rover's anonymized usage collection, you can set APOLLO_TELEMETRY_DISABLED=1
You can check out our documentation at https://go.apollo.dev/r/docs.
rover.exe is already installed, skipping installation.
schema
  @link(url: "https://specs.apollo.dev/link/v1.0")
{
  query: Query
  mutation: Mutation
}

extend schema
  @link(url: "https://specs.apollo.dev/federation/v2.0", import: ["@key", "@shareable"])

directive @link(url: String, as: String, for: link__Purpose, import: [link__Import]) repeatable on SCHEMA

directive @key(fields: federation__FieldSet!, resolvable: Boolean = true) repeatable on OBJECT | INTERFACE

directive @federation__requires(fields: federation__FieldSet!) on FIELD_DEFINITION

directive @federation__provides(fields: federation__FieldSet!) on FIELD_DEFINITION

directive @federation__external(reason: String) on OBJECT | FIELD_DEFINITION

directive @federation__tag(name: String!) repeatable on FIELD_DEFINITION | OBJECT | INTERFACE | UNION | ARGUMENT_DEFINITION | SCALAR | ENUM | ENUM_VALUE | INPUT_OBJECT | INPUT_FIELD_DEFINITION

directive @federation__extends on OBJECT | INTERFACE

directive @shareable on OBJECT | FIELD_DEFINITION
....

This message breaks schema:
If you would like to disable Rover's anonymized usage collection, you can set APOLLO_TELEMETRY_DISABLED=1
You can check out our documentation at https://go.apollo.dev/r/docs.
rover.exe is already installed, skipping installation.

[rplinzner]

The issue breaks our production pipelines and we couldn't deploy a quick fix. Lost couple of hairs trying to figure it out. PLS fix.

[kpachbiu88]

Temp solution install 0.7.0 version.
npm i @apollo/[email protected] -g

[rplinzner]

@kpachbiu88 Yes, figured it out, thx

[radekmie]

Can confirm, the same happens to us.

[abernix]

Thanks for opening this issue. Does this happen also to you all with the version installed from the curl installer? (Note: Specifically NOT from npm!).

In other words, the instruction at the top of the documentation here: https://www.apollographql.com/docs/rover/getting-started

[jazarja]

Also happened when composing supergraph

my command:

rover supergraph compose --config ./envs/supergraph-${{ env.ENVIRONMENT }}.yaml > schema.graphql

Why you guys need to display such annoying text when composing schema?

[abernix]

@jazarja The text is meant to be on STDERR and not interfere with the schema that's being generated. Also, I believe that text is just shown the first time you run Rover on an installation. If you run literally any other command first, that message might not appear? It looks to me like information from the installation step is bleeding into the output.

Out of curiosity, are you also installing Rover with npm? Or are you using the curl installer?

[radekmie]

@abernix I installed Rover CLI from npm (only there), but maybe had a curl version installed at some point too.

Also, I believe that text is just shown the first time you run Rover on an installation. If you run literally any other command first, that message might not appear? It looks to me like information from the installation step is bleeding into the output.

No, it's there every time.

[jazarja]

I install rover with npm on my github action (so it will always first time run whenever I run rover supergraph compose)

I can say the latest version has breaking change so the command to generate supergraph on https://www.apollographql.com/docs/rover/commands/supergraphs doesnt work anymore.

# Creates prod-schema.graphql or overwrites if it already exists
rover supergraph compose --config ./supergraph.yaml > prod-schema.graphql

[abernix]

Same question to everyone: can anyone confirm that the problem goes away with a version installed from curl instead of npm?

[radekmie]

It works correctly when installed using curl.

[kevin-mitchell]

I believe this is related to #1197