[bug]: Query Validation Doesn't Support Insecure Backends

[tjwiebell]

Describe the bug
Query validation that runs at build time will fail if the backend instance provided uses https but the certificate is self-signed or not trusted. Given query validation is a development build time activity where this setup would be common, we should allow insecure backends (similarly to how we ignore SSL errors for proxied requests to Magento).

To Reproduce
Steps to reproduce the behavior:

1. Setup insecure Magento backend
2. Configure this backend in .env
3. yarn build
4. See error

...
$ yarn run download-schema && graphql validate-magento-pwa-queries --project venia
$ graphql get-schema --project venia
⚠ request to https://magento-pwa.localhost/graphql failed, reason: certificate has expired
Validating GraphQL queries in venia project...
✖ An error occurred:
Could not find a schema at lastCachedGraphQLSchema.json.
...

Expected behavior
Query validation runs successfully and build completes

Possible solutions
Add insecure: true to packages/venia-concept/.graphqlconfig so the command graphql get-schema --project venia works with insecure Magento backends.

Please let us know what packages this bug is in regards to:

• venia-concept
• pwa-buildpack
• peregrine
• pwa-devdocs
• upward-js
• upward-spec

[LucasCalazans]

I've added the flag insecure: true but I'm getting the same issue.

yarn run build:

$ graphql get-schema --project venia
⚠ request to https://magento-pwa.localhost/graphql failed, reason: certificate has expired
Validating GraphQL queries in venia project...

My .graphqlconfig file (I'm not sure where I need to add this prop, so I've added in every node too 😄 ):

{
    "projects": {
        "venia": {
            "insecure": true,
            "schemaPath": "lastCachedGraphQLSchema.json",
            "extensions": {
                "endpoints": {
                    "default": "${env:MAGENTO_BACKEND_URL}/graphql"
                },
                "validate-magento-pwa-queries": {
                    "clients": ["apollo", "literal"],
                    "filesGlob": "src/**/*.{js,graphql,gql}"
                }
            }
        }
    }
}

[LucasCalazans]

Actually, it works.

I changed to HTTP in my .env file but my Nginx was redirecting to HTTPS.

[tjwiebell]

@LucasCalazans - I just pushed up PR #1313 with a working fix; looks like it was a CLI argument, not something you could configure in .graphqlconfig. As you've found, you can also just use an insecure backend.