Skip to content

Remote Schema Role Permission Definition Not Properly Formatted when too long  #7323

Open
@ericxiao251

Description

@ericxiao251

We require finer-grained permissions and this makes our remote_schema.yml file quite large with the number of permissions definitions per role.

We noticed that when creating the remote_schema.yml file from the UI, if the list of permissions becomes too long the permission definition section is formatted as a string and not in the proper YAML format.

This leads to problems when trying to use hasura metadata apply, so we have to manually re-format and tophat the yaml file before applying.

  - role: user
    definition:
      schema: |-
        schema  { query: Query mutation: Mutation }

        type Mutation { saveVideoResponse(id: String, input: VideoResponseInput!): Boolean!
        }

        type Query { _service: _Service
        }

        type _Service { sdl: String!
        }

        input VideoResponseInput {contactId: String!
          interactionLink: String!
        }
  - role: candidate
    definition:
      schema: "schema  { query: Query mutation: Mutation }\n\ntype Candidate { address:
        String\n  appliedTime: Float\n  bacbCertificationNumber: String\n  cityLocation:
        String\n  desiredStartDate: String\n  emailAddress: String!\n  employmentType:
	....

If this fix is accepted, I would love to write the code for it :).

Metadata

Metadata

Assignees

No one assigned

    Labels

    c/cliRelated to CLI

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions