[skip-stages=Flakey]
Change-Id: I6abefdfa9fed6dd4525c8786e93efa548b3710f2
Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/319603
Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
Reviewed-by: Isaac Moore <isaac.moore@instructure.com>
QA-Review: Jacob Burroughs <jburroughs@instructure.com>
Product-Review: Jacob Burroughs <jburroughs@instructure.com>
Build-Review: Jacob Burroughs <jburroughs@instructure.com>
Migration-Review: Jacob Burroughs <jburroughs@instructure.com>
fixes INTEROP-6951
upgrade required some tweaks including the following:
- `GraphQL::Execution::Interpreter` removed from CanvasSchema because
it is now included in GraphQL::Schema by default
- `BaseMutation.input_type` adds arguments properly instead of using
`merge!`, which blows up because `own_arguments` is a frozen Hash.
(see https://github.com/rmosolgo/graphql-ruby/commit/55a955a84)
- `NotificationPreferencesContextType` gets defined just once to avoid
errors from specifying dupicate enum values each time its reopened
- `.graphql_name` needed in a couple of places where `.name` (or
implicit `.to_s` from string interpolation) previously worked.
(see
https://github.com/rmosolgo/graphql-ruby/blob/master/CHANGELOG.md#breaking-changes-14)
- `GraphQL::Schema` uses the new `GrpahQL::Pagination::Connections`
connections by default (previously `GraphQL::Relay::BaseConnection`),
so our custom `PatchedArrayConnection` and `DynamoConnection` classes
got redone in accordance with the new interface.
- https://github.com/rmosolgo/graphql-ruby/pull/2792 made it so
argument names are used as-specified, while previously they were
automatically snake-cased. so the `gradingPeriodId` argument of
`AssignmentFilterInputType` is now specified in snake-case, and
everyone is happy. (note that in the generated GQL schema definition,
it remains camel-cased, so the client interface is unchanged).
- some sloppy queries in specs have been cleaned up because the GQL
parser has been tightened up and was no longer recognizing them.
also, unrelated to the gem bump, but the inst_access_tokens route was
typo'd as a singular. here it's corrected to the plural.
test plan:
- since it's just a version bump, spec coverage should be sufficient
Change-Id: Ib73eed4c1356833dfe245188b0841c98ae2c378a
Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/270132
Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
Reviewed-by: Ethan Vizitei <evizitei@instructure.com>
QA-Review: Michael Ziwisky <mziwisky@instructure.com>
Product-Review: Michael Ziwisky <mziwisky@instructure.com>
Test plan:
search for mutations between a date range using the mutation audit log
closes GQL-82
Change-Id: I99b7cba460261fe556073f3b5cc410dd1c3250e2
Reviewed-on: https://gerrit.instructure.com/205573
Tested-by: Jenkins
Reviewed-by: Rob Orton <rob@instructure.com>
QA-Review: Rob Orton <rob@instructure.com>
Product-Review: Rob Orton <rob@instructure.com>
closes GQL-59, GQL-63
refs GQL-46
Test plan:
* enable dynamodb
* do some mutations
* they should be queryable in the new audit log
Change-Id: I3b2753499c963fdbe3375079ffbd352285708cc7
Reviewed-on: https://gerrit.instructure.com/192138
Reviewed-by: Rob Orton <rob@instructure.com>
Reviewed-by: Landon Gilbert-Bland <lbland@instructure.com>
QA-Review: Rob Orton <rob@instructure.com>
Product-Review: Rob Orton <rob@instructure.com>
Tested-by: Jenkins
Jacob Burroughs