Philip Conrad

@olegroom You can get identical functionality by just checking to see if `graphql.parse_schema` succeeds. Example policy with helper function: ```rego import future.keywords.if # Example schema string: gql := ` type...

There's been a surprising amount of activity on this thread this morning! :sweat_smile: ----- > I would have expected that it would be cool to just add the `ValidateSchemaDocument` call...

Our gqlparser version is now updated to v2.5.0+, so it is now possible to add the `is_valid_schema` builtin discussed earlier in this thread. That will provide a small but useful...

This issue may be stale, but it's still an issue! :sweat_smile: Hopefully, I or someone else will have time to triage this issue in the parser soon.

Proposal for a quick-and-dirty implementation: ```rego aws.sigv4.sign_req(obj, aws_config) # Returns a signed request object for http.send(). ``` Where: - `obj`: Is the original request config object for [`http.send`][http-send] - `aws_config`:...

> Something like `providers.aws` or similar would be better I think. I figured that would be the most contentious/highest-revision part of the proposal! :sweat_smile: I have no objections to a...

@mlcooper I'd characterize the `graphql` builtins as fairly stable (we're not going to rip it out any time soon!), but the `graphql` APIs aren't exactly as user-friendly as most of...

The underlying issue here is that the parser has been treating unary minus parsing as _part of how numeric literals are parsed_ (ex: `-.05` is fine, but `-input.x` is not)....

I think I most agree with the "ideal solution" described above. :slightly_smiling_face: Allowing the user to pass through the `x-amz-content-sha256` header themselves (overriding any content hashing we do, or skipping...

If your goal is to generate a `string` that is the pre-signed URL, I think that might be a good case for a new builtin that simply shares a bunch...