2021-11-04 19:08:33 +03:00
|
|
|
module Hasura.Server.API.Metadata
|
|
|
|
|
( RQLMetadataV1 (..),
|
|
|
|
|
)
|
|
|
|
|
where
|
2021-07-07 04:43:42 +03:00
|
|
|
|
2023-03-30 18:13:42 +03:00
|
|
|
import Hasura.CustomReturnType.API qualified as CustomReturnType
|
2023-02-22 12:22:22 +03:00
|
|
|
import Hasura.LogicalModel.API qualified as LogicalModels
|
2021-07-07 04:43:42 +03:00
|
|
|
import Hasura.RQL.DDL.Action
|
|
|
|
|
import Hasura.RQL.DDL.ComputedField
|
2023-01-25 10:12:53 +03:00
|
|
|
import Hasura.RQL.DDL.ConnectionTemplate
|
2022-08-18 01:13:32 +03:00
|
|
|
import Hasura.RQL.DDL.DataConnector
|
2021-07-07 04:43:42 +03:00
|
|
|
import Hasura.RQL.DDL.EventTrigger
|
2023-01-23 16:35:48 +03:00
|
|
|
import Hasura.RQL.DDL.FeatureFlag
|
2021-07-07 04:43:42 +03:00
|
|
|
import Hasura.RQL.DDL.Metadata
|
|
|
|
|
import Hasura.RQL.DDL.Permission
|
2021-09-23 15:37:56 +03:00
|
|
|
import Hasura.RQL.DDL.QueryTags
|
Clean metadata arguments
## Description
Thanks to #1664, the Metadata API types no longer require a `ToJSON` instance. This PR follows up with a cleanup of the types of the arguments to the metadata API:
- whenever possible, it moves those argument types to where they're used (RQL.DDL.*)
- it removes all unrequired instances (mostly `ToJSON`)
This PR does not attempt to do it for _all_ such argument types. For some of the metadata operations, the type used to describe the argument to the API and used to represent the value in the metadata are one and the same (like for `CreateEndpoint`). Sometimes, the two types are intertwined in complex ways (`RemoteRelationship` and `RemoteRelationshipDef`). In the spirit of only doing uncontroversial cleaning work, this PR only moves types that are not used outside of RQL.DDL.
Furthermore, this is a small step towards separating the different types all jumbled together in RQL.Types.
## Notes
This PR also improves several `FromJSON` instances to make use of `withObject`, and to use a human readable string instead of a type name in error messages whenever possible. For instance:
- before: `expected Object for Object, but encountered X`
after: `expected Object for add computed field, but encountered X`
- before: `Expecting an object for update query`
after: `expected Object for update query, but encountered X`
This PR also renames `CreateFunctionPermission` to `FunctionPermissionArgument`, to remove the quite surprising `type DropFunctionPermission = CreateFunctionPermission`.
This PR also deletes some dead code, mostly in RQL.DML.
This PR also moves a PG-specific source resolving function from DDL.Schema.Source to the only place where it is used: App.hs.
https://github.com/hasura/graphql-engine-mono/pull/1844
GitOrigin-RevId: a594521194bb7fe6a111b02a9e099896f9fed59c
2021-07-27 13:41:42 +03:00
|
|
|
import Hasura.RQL.DDL.Relationship
|
|
|
|
|
import Hasura.RQL.DDL.Relationship.Rename
|
2023-01-09 10:25:32 +03:00
|
|
|
import Hasura.RQL.DDL.Relationship.Suggest
|
Clean metadata arguments
## Description
Thanks to #1664, the Metadata API types no longer require a `ToJSON` instance. This PR follows up with a cleanup of the types of the arguments to the metadata API:
- whenever possible, it moves those argument types to where they're used (RQL.DDL.*)
- it removes all unrequired instances (mostly `ToJSON`)
This PR does not attempt to do it for _all_ such argument types. For some of the metadata operations, the type used to describe the argument to the API and used to represent the value in the metadata are one and the same (like for `CreateEndpoint`). Sometimes, the two types are intertwined in complex ways (`RemoteRelationship` and `RemoteRelationshipDef`). In the spirit of only doing uncontroversial cleaning work, this PR only moves types that are not used outside of RQL.DDL.
Furthermore, this is a small step towards separating the different types all jumbled together in RQL.Types.
## Notes
This PR also improves several `FromJSON` instances to make use of `withObject`, and to use a human readable string instead of a type name in error messages whenever possible. For instance:
- before: `expected Object for Object, but encountered X`
after: `expected Object for add computed field, but encountered X`
- before: `Expecting an object for update query`
after: `expected Object for update query, but encountered X`
This PR also renames `CreateFunctionPermission` to `FunctionPermissionArgument`, to remove the quite surprising `type DropFunctionPermission = CreateFunctionPermission`.
This PR also deletes some dead code, mostly in RQL.DML.
This PR also moves a PG-specific source resolving function from DDL.Schema.Source to the only place where it is used: App.hs.
https://github.com/hasura/graphql-engine-mono/pull/1844
GitOrigin-RevId: a594521194bb7fe6a111b02a9e099896f9fed59c
2021-07-27 13:41:42 +03:00
|
|
|
import Hasura.RQL.DDL.RemoteRelationship
|
2021-07-07 04:43:42 +03:00
|
|
|
import Hasura.RQL.DDL.Schema
|
Clean metadata arguments
## Description
Thanks to #1664, the Metadata API types no longer require a `ToJSON` instance. This PR follows up with a cleanup of the types of the arguments to the metadata API:
- whenever possible, it moves those argument types to where they're used (RQL.DDL.*)
- it removes all unrequired instances (mostly `ToJSON`)
This PR does not attempt to do it for _all_ such argument types. For some of the metadata operations, the type used to describe the argument to the API and used to represent the value in the metadata are one and the same (like for `CreateEndpoint`). Sometimes, the two types are intertwined in complex ways (`RemoteRelationship` and `RemoteRelationshipDef`). In the spirit of only doing uncontroversial cleaning work, this PR only moves types that are not used outside of RQL.DDL.
Furthermore, this is a small step towards separating the different types all jumbled together in RQL.Types.
## Notes
This PR also improves several `FromJSON` instances to make use of `withObject`, and to use a human readable string instead of a type name in error messages whenever possible. For instance:
- before: `expected Object for Object, but encountered X`
after: `expected Object for add computed field, but encountered X`
- before: `Expecting an object for update query`
after: `expected Object for update query, but encountered X`
This PR also renames `CreateFunctionPermission` to `FunctionPermissionArgument`, to remove the quite surprising `type DropFunctionPermission = CreateFunctionPermission`.
This PR also deletes some dead code, mostly in RQL.DML.
This PR also moves a PG-specific source resolving function from DDL.Schema.Source to the only place where it is used: App.hs.
https://github.com/hasura/graphql-engine-mono/pull/1844
GitOrigin-RevId: a594521194bb7fe6a111b02a9e099896f9fed59c
2021-07-27 13:41:42 +03:00
|
|
|
import Hasura.RQL.DDL.Schema.Source
|
2022-08-18 01:13:32 +03:00
|
|
|
import Hasura.RQL.DDL.SourceKinds
|
2022-03-11 02:22:54 +03:00
|
|
|
import Hasura.RQL.DDL.Webhook.Transform.Validation
|
2022-04-27 16:57:28 +03:00
|
|
|
import Hasura.RQL.Types.Allowlist
|
|
|
|
|
import Hasura.RQL.Types.ApiLimit
|
|
|
|
|
import Hasura.RQL.Types.Common
|
|
|
|
|
import Hasura.RQL.Types.CustomTypes
|
2022-03-13 10:40:06 +03:00
|
|
|
import Hasura.RQL.Types.Endpoint
|
2022-09-09 11:26:44 +03:00
|
|
|
import Hasura.RQL.Types.EventTrigger
|
2022-04-27 16:57:28 +03:00
|
|
|
import Hasura.RQL.Types.GraphqlSchemaIntrospection
|
|
|
|
|
import Hasura.RQL.Types.Metadata
|
|
|
|
|
import Hasura.RQL.Types.Network
|
2022-11-23 05:49:29 +03:00
|
|
|
import Hasura.RQL.Types.OpenTelemetry
|
2022-04-27 16:57:28 +03:00
|
|
|
import Hasura.RQL.Types.QueryCollection
|
|
|
|
|
import Hasura.RQL.Types.Roles
|
|
|
|
|
import Hasura.RQL.Types.ScheduledTrigger
|
scaffolding for remote-schemas module
The main aim of the PR is:
1. To set up a module structure for 'remote-schemas' package.
2. Move parts by the remote schema codebase into the new module structure to validate it.
## Notes to the reviewer
Why a PR with large-ish diff?
1. We've been making progress on the MM project but we don't yet know long it is going to take us to get to the first milestone. To understand this better, we need to figure out the unknowns as soon as possible. Hence I've taken a stab at the first two items in the [end-state](https://gist.github.com/0x777/ca2bdc4284d21c3eec153b51dea255c9) document to figure out the unknowns. Unsurprisingly, there are a bunch of issues that we haven't discussed earlier. These are documented in the 'open questions' section.
1. The diff is large but that is only code moved around and I've added a section that documents how things are moved. In addition, there are fair number of PR comments to help with the review process.
## Changes in the PR
### Module structure
Sets up the module structure as follows:
```
Hasura/
RemoteSchema/
Metadata/
Types.hs
SchemaCache/
Types.hs
Permission.hs
RemoteRelationship.hs
Build.hs
MetadataAPI/
Types.hs
Execute.hs
```
### 1. Types representing metadata are moved
Types that capture metadata information (currently scattered across several RQL modules) are moved into `Hasura.RemoteSchema.Metadata.Types`.
- This new module only depends on very 'core' modules such as
`Hasura.Session` for the notion of roles and `Hasura.Incremental` for `Cacheable` typeclass.
- The requirement on database modules is avoided by generalizing the remote schemas metadata to accept an arbitrary 'r' for a remote relationship
definition.
### 2. SchemaCache related types and build logic have been moved
Types that represent remote schemas information in SchemaCache are moved into `Hasura.RemoteSchema.SchemaCache.Types`.
Similar to `H.RS.Metadata.Types`, this module depends on 'core' modules except for `Hasura.GraphQL.Parser.Variable`. It has something to do with remote relationships but I haven't spent time looking into it. The validation of 'remote relationships to remote schema' is also something that needs to be looked at.
Rips out the logic that builds remote schema's SchemaCache information from the monolithic `buildSchemaCacheRule` and moves it into `Hasura.RemoteSchema.SchemaCache.Build`. Further, the `.SchemaCache.Permission` and `.SchemaCache.RemoteRelationship` have been created from existing modules that capture schema cache building logic for those two components.
This was a fair amount of work. On main, currently remote schema's SchemaCache information is built in two phases - in the first phase, 'permissions' and 'remote relationships' are ignored and in the second phase they are filled in.
While remote relationships can only be resolved after partially resolving sources and other remote schemas, the same isn't true for permissions. Further, most of the work that is done to resolve remote relationships can be moved to the first phase so that the second phase can be a very simple traversal.
This is the approach that was taken - resolve permissions and as much as remote relationships information in the first phase.
### 3. Metadata APIs related types and build logic have been moved
The types that represent remote schema related metadata APIs and the execution logic have been moved to `Hasura.RemoteSchema.MetadataAPI.Types` and `.Execute` modules respectively.
## Open questions:
1. `Hasura.RemoteSchema.Metadata.Types` is so called because I was hoping that all of the metadata related APIs of remote schema can be brought in at `Hasura.RemoteSchema.Metadata.API`. However, as metadata APIs depended on functions from `SchemaCache` module (see [1](https://github.com/hasura/graphql-engine-mono/blob/ceba6d62264603ee5d279814677b29bcc43ecaea/server/src-lib/Hasura/RQL/DDL/RemoteSchema.hs#L55) and [2](https://github.com/hasura/graphql-engine-mono/blob/ceba6d62264603ee5d279814677b29bcc43ecaea/server/src-lib/Hasura/RQL/DDL/RemoteSchema.hs#L91), it made more sense to create a separate top-level module for `MetadataAPI`s.
Maybe we can just have `Hasura.RemoteSchema.Metadata` and get rid of the extra nesting or have `Hasura.RemoteSchema.Metadata.{Core,Permission,RemoteRelationship}` if we want to break them down further.
1. `buildRemoteSchemas` in `H.RS.SchemaCache.Build` has the following type:
```haskell
buildRemoteSchemas ::
( ArrowChoice arr,
Inc.ArrowDistribute arr,
ArrowWriter (Seq CollectedInfo) arr,
Inc.ArrowCache m arr,
MonadIO m,
HasHttpManagerM m,
Inc.Cacheable remoteRelationshipDefinition,
ToJSON remoteRelationshipDefinition,
MonadError QErr m
) =>
Env.Environment ->
( (Inc.Dependency (HashMap RemoteSchemaName Inc.InvalidationKey), OrderedRoles),
[RemoteSchemaMetadataG remoteRelationshipDefinition]
)
`arr` HashMap RemoteSchemaName (PartiallyResolvedRemoteSchemaCtxG remoteRelationshipDefinition, MetadataObject)
```
Note the dependence on `CollectedInfo` which is defined as
```haskell
data CollectedInfo
= CIInconsistency InconsistentMetadata
| CIDependency
MetadataObject
-- ^ for error reporting on missing dependencies
SchemaObjId
SchemaDependency
deriving (Eq)
```
this pretty much means that remote schemas is dependent on types from databases, actions, ....
How do we fix this? Maybe introduce a typeclass such as `ArrowCollectRemoteSchemaDependencies` which is defined in `Hasura.RemoteSchema` and then implemented in graphql-engine?
1. The dependency on `buildSchemaCacheFor` in `.MetadataAPI.Execute` which has the following signature:
```haskell
buildSchemaCacheFor ::
(QErrM m, CacheRWM m, MetadataM m) =>
MetadataObjId ->
MetadataModifier ->
```
This can be easily resolved if we restrict what the metadata APIs are allowed to do. Currently, they operate in an unfettered access to modify SchemaCache (the `CacheRWM` constraint):
```haskell
runAddRemoteSchema ::
( QErrM m,
CacheRWM m,
MonadIO m,
HasHttpManagerM m,
MetadataM m,
Tracing.MonadTrace m
) =>
Env.Environment ->
AddRemoteSchemaQuery ->
m EncJSON
```
This should instead be changed to restrict remote schema APIs to only modify remote schema metadata (but has access to the remote schemas part of the schema cache), this dependency is completely removed.
```haskell
runAddRemoteSchema ::
( QErrM m,
MonadIO m,
HasHttpManagerM m,
MonadReader RemoteSchemasSchemaCache m,
MonadState RemoteSchemaMetadata m,
Tracing.MonadTrace m
) =>
Env.Environment ->
AddRemoteSchemaQuery ->
m RemoteSchemeMetadataObjId
```
The idea is that the core graphql-engine would call these functions and then call
`buildSchemaCacheFor`.
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6291
GitOrigin-RevId: 51357148c6404afe70219afa71bd1d59bdf4ffc6
2022-10-21 06:13:07 +03:00
|
|
|
import Hasura.RemoteSchema.MetadataAPI
|
2021-07-07 04:43:42 +03:00
|
|
|
import Hasura.SQL.AnyBackend
|
|
|
|
|
|
|
|
|
|
data RQLMetadataV1
|
|
|
|
|
= -- Sources
|
|
|
|
|
RMAddSource !(AnyBackend AddSource)
|
|
|
|
|
| RMDropSource DropSource
|
|
|
|
|
| RMRenameSource !RenameSource
|
2022-06-22 10:06:19 +03:00
|
|
|
| RMUpdateSource !(AnyBackend UpdateSource)
|
2022-08-30 02:51:34 +03:00
|
|
|
| RMListSourceKinds !ListSourceKinds
|
2022-09-02 20:50:09 +03:00
|
|
|
| RMGetSourceKindCapabilities !GetSourceKindCapabilities
|
2022-08-30 02:51:34 +03:00
|
|
|
| RMGetSourceTables !GetSourceTables
|
|
|
|
|
| RMGetTableInfo !GetTableInfo
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Tables
|
|
|
|
|
RMTrackTable !(AnyBackend TrackTableV2)
|
|
|
|
|
| RMUntrackTable !(AnyBackend UntrackTable)
|
|
|
|
|
| RMSetTableCustomization !(AnyBackend SetTableCustomization)
|
2022-08-04 12:35:58 +03:00
|
|
|
| RMSetApolloFederationConfig (AnyBackend SetApolloFederationConfig)
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Tables (PG-specific)
|
2022-10-11 12:08:04 +03:00
|
|
|
RMPgSetTableIsEnum !(AnyBackend SetTableIsEnum)
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Tables permissions
|
|
|
|
|
RMCreateInsertPermission !(AnyBackend (CreatePerm InsPerm))
|
|
|
|
|
| RMCreateSelectPermission !(AnyBackend (CreatePerm SelPerm))
|
|
|
|
|
| RMCreateUpdatePermission !(AnyBackend (CreatePerm UpdPerm))
|
|
|
|
|
| RMCreateDeletePermission !(AnyBackend (CreatePerm DelPerm))
|
2022-04-06 15:47:35 +03:00
|
|
|
| RMDropInsertPermission !(AnyBackend DropPerm)
|
|
|
|
|
| RMDropSelectPermission !(AnyBackend DropPerm)
|
|
|
|
|
| RMDropUpdatePermission !(AnyBackend DropPerm)
|
|
|
|
|
| RMDropDeletePermission !(AnyBackend DropPerm)
|
2021-07-07 04:43:42 +03:00
|
|
|
| RMSetPermissionComment !(AnyBackend SetPermComment)
|
|
|
|
|
| -- Tables relationships
|
|
|
|
|
RMCreateObjectRelationship !(AnyBackend CreateObjRel)
|
|
|
|
|
| RMCreateArrayRelationship !(AnyBackend CreateArrRel)
|
|
|
|
|
| RMDropRelationship !(AnyBackend DropRel)
|
|
|
|
|
| RMSetRelationshipComment !(AnyBackend SetRelComment)
|
|
|
|
|
| RMRenameRelationship !(AnyBackend RenameRel)
|
2023-01-09 10:25:32 +03:00
|
|
|
| RMSuggestRelationships !(AnyBackend SuggestRels)
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Tables remote relationships
|
2021-12-01 07:53:34 +03:00
|
|
|
RMCreateRemoteRelationship !(AnyBackend CreateFromSourceRelationship)
|
|
|
|
|
| RMUpdateRemoteRelationship !(AnyBackend CreateFromSourceRelationship)
|
Fix several issues with remote relationships.
## Remaining Work
- [x] changelog entry
- [x] more tests: `<backend>_delete_remote_relationship` is definitely untested
- [x] negative tests: we probably want to assert that there are some APIs we DON'T support
- [x] update the console to use the new API, if necessary
- [x] ~~adding the corresponding documentation for the API for other backends (only `pg_` was added here)~~
- deferred to https://github.com/hasura/graphql-engine-mono/issues/3170
- [x] ~~deciding which backends should support this API~~
- deferred to https://github.com/hasura/graphql-engine-mono/issues/3170
- [x] ~~deciding what to do about potentially overlapping schematic representations~~
- ~~cf. https://github.com/hasura/graphql-engine-mono/pull/3157#issuecomment-995307624~~
- deferred to https://github.com/hasura/graphql-engine-mono/issues/3171
- [x] ~~add more descriptive versioning information to some of the types that are changing in this PR~~
- cf. https://github.com/hasura/graphql-engine-mono/pull/3157#discussion_r769830920
- deferred to https://github.com/hasura/graphql-engine-mono/issues/3172
## Description
This PR fixes several important issues wrt. the remote relationship API.
- it fixes a regression introduced by [#3124](https://github.com/hasura/graphql-engine-mono/pull/3124), which prevented `<backend>_create_remote_relationship` from accepting the old argument format (break of backwards compatibility, broke the console)
- it removes the command `create_remote_relationship` added to the v1/metadata API as a work-around as part of [#3124](https://github.com/hasura/graphql-engine-mono/pull/3124)
- it reverts the subsequent fix in the console: [#3149](https://github.com/hasura/graphql-engine-mono/pull/3149)
Furthermore, this PR also addresses two other issues:
- THE DOCUMENTATION OF THE METADATA API WAS WRONG, and documented `create_remote_relationship` instead of `<backend>_create_remote_relationship`: this PR fixes this by adding `pg_` everywhere, but does not attempt to add the corresponding documentation for other backends, partly because:
- `<backend>_delete_remote_relationship` WAS BROKEN ON NON-POSTGRES BACKENDS; it always expected an argument parameterized by Postgres.
As of main, the `<backend>_(create|update|delete)_remote_relationship` commands are supported on Postgres, Citus, BigQuery, but **NOT MSSQL**. I do not know if this is intentional or not, if it even should be publicized or not, and as a result this PR doesn't change this.
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3157
Co-authored-by: jkachmar <8461423+jkachmar@users.noreply.github.com>
GitOrigin-RevId: 37e2f41522a9229a11c595574c3f4984317d652a
2021-12-16 23:28:08 +03:00
|
|
|
| RMDeleteRemoteRelationship !(AnyBackend DeleteFromSourceRelationship)
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Functions
|
|
|
|
|
RMTrackFunction !(AnyBackend TrackFunctionV2)
|
|
|
|
|
| RMUntrackFunction !(AnyBackend UnTrackFunction)
|
2021-10-07 16:02:19 +03:00
|
|
|
| RMSetFunctionCustomization (AnyBackend SetFunctionCustomization)
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Functions permissions
|
Clean metadata arguments
## Description
Thanks to #1664, the Metadata API types no longer require a `ToJSON` instance. This PR follows up with a cleanup of the types of the arguments to the metadata API:
- whenever possible, it moves those argument types to where they're used (RQL.DDL.*)
- it removes all unrequired instances (mostly `ToJSON`)
This PR does not attempt to do it for _all_ such argument types. For some of the metadata operations, the type used to describe the argument to the API and used to represent the value in the metadata are one and the same (like for `CreateEndpoint`). Sometimes, the two types are intertwined in complex ways (`RemoteRelationship` and `RemoteRelationshipDef`). In the spirit of only doing uncontroversial cleaning work, this PR only moves types that are not used outside of RQL.DDL.
Furthermore, this is a small step towards separating the different types all jumbled together in RQL.Types.
## Notes
This PR also improves several `FromJSON` instances to make use of `withObject`, and to use a human readable string instead of a type name in error messages whenever possible. For instance:
- before: `expected Object for Object, but encountered X`
after: `expected Object for add computed field, but encountered X`
- before: `Expecting an object for update query`
after: `expected Object for update query, but encountered X`
This PR also renames `CreateFunctionPermission` to `FunctionPermissionArgument`, to remove the quite surprising `type DropFunctionPermission = CreateFunctionPermission`.
This PR also deletes some dead code, mostly in RQL.DML.
This PR also moves a PG-specific source resolving function from DDL.Schema.Source to the only place where it is used: App.hs.
https://github.com/hasura/graphql-engine-mono/pull/1844
GitOrigin-RevId: a594521194bb7fe6a111b02a9e099896f9fed59c
2021-07-27 13:41:42 +03:00
|
|
|
RMCreateFunctionPermission !(AnyBackend FunctionPermissionArgument)
|
|
|
|
|
| RMDropFunctionPermission !(AnyBackend FunctionPermissionArgument)
|
2022-05-04 17:52:29 +03:00
|
|
|
| -- Computed fields
|
|
|
|
|
RMAddComputedField !(AnyBackend AddComputedField)
|
|
|
|
|
| RMDropComputedField !(AnyBackend DropComputedField)
|
2023-01-25 10:12:53 +03:00
|
|
|
| -- Connection template
|
|
|
|
|
RMTestConnectionTemplate !(AnyBackend TestConnectionTemplate)
|
2023-02-21 16:45:12 +03:00
|
|
|
| -- Logical Models
|
|
|
|
|
RMGetLogicalModel !(AnyBackend LogicalModels.GetLogicalModel)
|
|
|
|
|
| RMTrackLogicalModel !(AnyBackend LogicalModels.TrackLogicalModel)
|
|
|
|
|
| RMUntrackLogicalModel !(AnyBackend LogicalModels.UntrackLogicalModel)
|
2023-03-03 18:27:51 +03:00
|
|
|
| RMCreateSelectLogicalModelPermission !(AnyBackend (LogicalModels.CreateLogicalModelPermission SelPerm))
|
2023-03-03 20:58:22 +03:00
|
|
|
| RMDropSelectLogicalModelPermission !(AnyBackend LogicalModels.DropLogicalModelPermission)
|
2023-03-30 18:13:42 +03:00
|
|
|
| -- Custom types
|
|
|
|
|
RMGetCustomReturnType !(AnyBackend CustomReturnType.GetCustomReturnType)
|
|
|
|
|
| RMTrackCustomReturnType !(AnyBackend CustomReturnType.TrackCustomReturnType)
|
|
|
|
|
| RMUntrackCustomReturnType !(AnyBackend CustomReturnType.UntrackCustomReturnType)
|
2023-03-31 19:27:49 +03:00
|
|
|
| RMCreateSelectCustomReturnTypePermission !(AnyBackend (CustomReturnType.CreateCustomReturnTypePermission SelPerm))
|
|
|
|
|
| RMDropSelectCustomReturnTypePermission !(AnyBackend CustomReturnType.DropCustomReturnTypePermission)
|
2021-09-09 14:54:19 +03:00
|
|
|
| -- Tables event triggers
|
2022-03-11 02:22:54 +03:00
|
|
|
RMCreateEventTrigger !(AnyBackend (Unvalidated1 CreateEventTriggerQuery))
|
2021-09-09 14:54:19 +03:00
|
|
|
| RMDeleteEventTrigger !(AnyBackend DeleteEventTriggerQuery)
|
|
|
|
|
| RMRedeliverEvent !(AnyBackend RedeliverEventQuery)
|
2021-09-06 14:15:36 +03:00
|
|
|
| RMInvokeEventTrigger !(AnyBackend InvokeEventTriggerQuery)
|
2022-09-09 11:26:44 +03:00
|
|
|
| RMCleanupEventTriggerLog !TriggerLogCleanupConfig
|
2022-09-21 08:59:14 +03:00
|
|
|
| RMResumeEventTriggerCleanup !TriggerLogCleanupToggleConfig
|
2022-09-13 11:33:44 +03:00
|
|
|
| RMPauseEventTriggerCleanup !TriggerLogCleanupToggleConfig
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Remote schemas
|
|
|
|
|
RMAddRemoteSchema !AddRemoteSchemaQuery
|
|
|
|
|
| RMUpdateRemoteSchema !AddRemoteSchemaQuery
|
|
|
|
|
| RMRemoveRemoteSchema !RemoteSchemaNameQuery
|
|
|
|
|
| RMReloadRemoteSchema !RemoteSchemaNameQuery
|
|
|
|
|
| RMIntrospectRemoteSchema !RemoteSchemaNameQuery
|
|
|
|
|
| -- Remote schemas permissions
|
2021-08-09 13:20:04 +03:00
|
|
|
RMAddRemoteSchemaPermissions !AddRemoteSchemaPermission
|
2021-07-07 04:43:42 +03:00
|
|
|
| RMDropRemoteSchemaPermissions !DropRemoteSchemaPermissions
|
2022-03-17 23:53:56 +03:00
|
|
|
| -- Remote Schema remote relationships
|
|
|
|
|
RMCreateRemoteSchemaRemoteRelationship CreateRemoteSchemaRemoteRelationship
|
|
|
|
|
| RMUpdateRemoteSchemaRemoteRelationship CreateRemoteSchemaRemoteRelationship
|
|
|
|
|
| RMDeleteRemoteSchemaRemoteRelationship DeleteRemoteSchemaRemoteRelationship
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Scheduled triggers
|
2022-03-11 02:22:54 +03:00
|
|
|
RMCreateCronTrigger !(Unvalidated CreateCronTrigger)
|
2021-07-07 04:43:42 +03:00
|
|
|
| RMDeleteCronTrigger !ScheduledTriggerName
|
|
|
|
|
| RMCreateScheduledEvent !CreateScheduledEvent
|
|
|
|
|
| RMDeleteScheduledEvent !DeleteScheduledEvent
|
|
|
|
|
| RMGetScheduledEvents !GetScheduledEvents
|
2022-11-03 13:21:56 +03:00
|
|
|
| RMGetScheduledEventInvocations !GetScheduledEventInvocations
|
2022-01-27 09:43:39 +03:00
|
|
|
| RMGetCronTriggers
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Actions
|
2022-03-11 02:22:54 +03:00
|
|
|
RMCreateAction !(Unvalidated CreateAction)
|
2021-07-07 04:43:42 +03:00
|
|
|
| RMDropAction !DropAction
|
2022-03-11 02:22:54 +03:00
|
|
|
| RMUpdateAction !(Unvalidated UpdateAction)
|
2021-07-07 04:43:42 +03:00
|
|
|
| RMCreateActionPermission !CreateActionPermission
|
|
|
|
|
| RMDropActionPermission !DropActionPermission
|
|
|
|
|
| -- Query collections, allow list related
|
|
|
|
|
RMCreateQueryCollection !CreateCollection
|
2022-08-19 16:36:02 +03:00
|
|
|
| RMRenameQueryCollection !RenameCollection
|
2021-07-07 04:43:42 +03:00
|
|
|
| RMDropQueryCollection !DropCollection
|
|
|
|
|
| RMAddQueryToCollection !AddQueryToCollection
|
|
|
|
|
| RMDropQueryFromCollection !DropQueryFromCollection
|
2022-02-08 19:53:30 +03:00
|
|
|
| RMAddCollectionToAllowlist !AllowlistEntry
|
|
|
|
|
| RMDropCollectionFromAllowlist !DropCollectionFromAllowlist
|
|
|
|
|
| RMUpdateScopeOfCollectionInAllowlist !UpdateScopeOfCollectionInAllowlist
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Rest endpoints
|
|
|
|
|
RMCreateRestEndpoint !CreateEndpoint
|
|
|
|
|
| RMDropRestEndpoint !DropEndpoint
|
2022-08-18 01:13:32 +03:00
|
|
|
| -- GraphQL Data Connectors
|
|
|
|
|
RMDCAddAgent !DCAddAgent
|
|
|
|
|
| RMDCDeleteAgent !DCDeleteAgent
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Custom types
|
|
|
|
|
RMSetCustomTypes !CustomTypes
|
|
|
|
|
| -- Api limits
|
|
|
|
|
RMSetApiLimits !ApiLimit
|
|
|
|
|
| RMRemoveApiLimits
|
|
|
|
|
| -- Metrics config
|
|
|
|
|
RMSetMetricsConfig !MetricsConfig
|
|
|
|
|
| RMRemoveMetricsConfig
|
|
|
|
|
| -- Inherited roles
|
2021-07-17 00:18:58 +03:00
|
|
|
RMAddInheritedRole !InheritedRole
|
2021-07-07 04:43:42 +03:00
|
|
|
| RMDropInheritedRole !DropInheritedRole
|
|
|
|
|
| -- Metadata management
|
|
|
|
|
RMReplaceMetadata !ReplaceMetadata
|
|
|
|
|
| RMExportMetadata !ExportMetadata
|
|
|
|
|
| RMClearMetadata !ClearMetadata
|
|
|
|
|
| RMReloadMetadata !ReloadMetadata
|
|
|
|
|
| RMGetInconsistentMetadata !GetInconsistentMetadata
|
|
|
|
|
| RMDropInconsistentMetadata !DropInconsistentMetadata
|
|
|
|
|
| -- Introspection options
|
|
|
|
|
RMSetGraphqlSchemaIntrospectionOptions !SetGraphqlIntrospectionOptions
|
2021-08-24 10:36:32 +03:00
|
|
|
| -- Network
|
|
|
|
|
RMAddHostToTLSAllowlist !AddHostToTLSAllowlist
|
|
|
|
|
| RMDropHostFromTLSAllowlist !DropHostFromTLSAllowlist
|
2021-09-23 15:37:56 +03:00
|
|
|
| -- QueryTags
|
|
|
|
|
RMSetQueryTagsConfig !SetQueryTagsConfig
|
2022-11-23 05:49:29 +03:00
|
|
|
| -- OpenTelemetry
|
|
|
|
|
RMSetOpenTelemetryConfig !OpenTelemetryConfig
|
|
|
|
|
| RMSetOpenTelemetryStatus !OtelStatus
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Debug
|
|
|
|
|
RMDumpInternalState !DumpInternalState
|
|
|
|
|
| RMGetCatalogState !GetCatalogState
|
|
|
|
|
| RMSetCatalogState !SetCatalogState
|
2022-03-11 02:22:54 +03:00
|
|
|
| RMTestWebhookTransform !(Unvalidated TestWebhookTransform)
|
2023-01-23 16:35:48 +03:00
|
|
|
| -- Feature Flags
|
|
|
|
|
RMGetFeatureFlag !GetFeatureFlag
|
2021-07-07 04:43:42 +03:00
|
|
|
| -- Bulk metadata queries
|
|
|
|
|
RMBulk [RQLMetadataRequest]
|
|
|
|
|
|
|
|
|
|
data RQLMetadataV2
|
|
|
|
|
= RMV2ReplaceMetadata !ReplaceMetadataV2
|
|
|
|
|
| RMV2ExportMetadata !ExportMetadata
|
|
|
|
|
|
|
|
|
|
data RQLMetadataRequest
|
|
|
|
|
= RMV1 !RQLMetadataV1
|
|
|
|
|
| RMV2 !RQLMetadataV2
|
