v0.2.0

uses: github.com/mozership/probe-graphql@41e4ffa222db58c63c7169117c919e6d252bdbf9 # v0.2.0

Highlights

• The action now keeps to the guard of a run, and its action.yml declares guard: [read-only, allow-host], so Probe v1.21.0 or later runs it under --read-only and --allow-host without --allow-action.
• Its action.yml declares params, so probe check reports a key of with the action does not take.
• A key of with the action does not take now fails the step.

Keeping to the guard

The action used to keep to no guard, so a step that used it was refused under --read-only or --allow-host unless --allow-action named it. It now refuses, before anything is sent, what the guard does not allow, and the step fails with the kind refused:

• Under --read-only, only a query is sent. The operation to run, the one operation_name names or the only one in the document, is read with gqlparser. A mutation or a subscription is refused, and so is a document that does not parse, one with several operations and no operation_name, and an operation_name the document does not have.
• Under --allow-host, the host of url, and of each redirect, must be one the run allows. A URL without a port is taken at the port of its scheme.

Parameters

params: [url, query, variables, operation_name, headers, timeout] in action.yml lets probe check report a misspelled key with its line. The action checks the same list itself, so a key that is not one of them fails the step before anything is sent; it used to be ignored.

Requirements

The action runs on Probe v1.17.0 or later as before. Running it under a guard, and having probe check check its with, need Probe v1.21.0 or later. See GraphQL.

Changelog

• 18e0ed3 Keep to the guard of a run, and declare it and the params in action.yml
• b571ec3 Merge pull request #2 from mozership/keep-to-the-guard
• ad456d1 Point action.yml at v0.1.1