-
-
Notifications
You must be signed in to change notification settings - Fork 206
Description
Issue workflow progress
Progress of the issue based on the
Contributor Workflow
- 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox
Make sure to fork this template and run
pnpm generatein the terminal.Please make sure the Codegen and plugins version under
package.jsonmatches yours. - 2. A failing test has been provided
- 3. A local solution has been provided
- 4. A pull request is pending review
Describe the bug
We output a URL from a previous step that we use as the input so that we can check a schema.gql file against one of our environments (dev, staging and prod). This usually fails, for whatever reason, often with a message like:
Error: Invalid or incomplete introspection result. Ensure that you are passing "data" property of introspection response and no "errors" was returned alongside: undefined., but I can access the site and fetch the introspection schema just fine (tested inside the github runner as well). Somehow, this comes out undefined.
This is what the step looks like:
Run kamilkisiela/graphql-inspector@master
with:
approve-label: breaking-schema-change
fail-on-breaking: true
name: ext.ourdomain.com
schema: app/javascript/graphql/src/schema/schema_external.gql
endpoint: https://ext.ourdomain.com/graphql
rules: ignoreDescriptionChanges
suppressRemovalOfDeprecatedField
safeUnreachable
github-token: ***
env:
GH_TOKEN: ***
CURRENT_BRANCH_NAME: maintenance/external-schema
TARGET_BRANCH_NAME: develop
source_endpoint: app/javascript/graphql/src/schema/schema.gql
source_endpoint_ext: app/javascript/graphql/src/schema/schema_external.gql
target_environment: development
GraphQL Inspector started
Creating a check named "ext.ourdomain.com"
EXPERIMENTAL - Using Pull Request refs/pull/10248/merge
EXPERIMENTAL - Using develop as base schema ref
To Reproduce Steps to reproduce the behavior:
Set up multiple steps validating different schema files against different URLs output from a previous step.
Expected behavior
Schema to be fetched correctly every time.
Environment:
- Github Actions with ubuntu-latest (or our custom Github Actions Runners, it doesnt matter, its the same issue)
- kamilkisiela/graphql-inspector@master