mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 20:41:49 +03:00
81 lines
3.1 KiB
ReStructuredText
81 lines
3.1 KiB
ReStructuredText
Setting default values for fields using role based column presets
|
|
=================================================================
|
|
|
|
.. contents:: Table of contents
|
|
:backlinks: none
|
|
:depth: 1
|
|
:local:
|
|
|
|
Let's say you want certain fields to have their values set automatically when not explicitly passed using session
|
|
variables or fixed values when a new row is created with a particular :doc:`user role <../../auth/roles-variables>`
|
|
|
|
Hasura GraphQL engine's column presets let you define role-based default values for any field/column. These values can either
|
|
be an Authorization header's value or a static value.
|
|
|
|
.. admonition:: Column preset restricts mutation access for configured role
|
|
|
|
If a column has a preset defined for a given role, access to the column for mutations will be restricted for users
|
|
with said role.
|
|
|
|
**Example:** Say we have a field ``user_id`` in a table ``article`` which is to be set to the id of the user, from
|
|
the value of the user's Authorization header whenever a new row is added to the ``article`` table.
|
|
|
|
Step 1: Configure a column preset
|
|
---------------------------------
|
|
|
|
The column preset option is available under the ``Permissions`` tab of a table. Open the console and head to
|
|
``Data -> article -> Permissions``:
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/column-presets-option.png
|
|
|
|
Enable the column preset option to define presets for one or more columns. For each column, you can pick between
|
|
setting the preset using a static value or from a session variable.
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/column-presets-value-options.png
|
|
|
|
For our chosen example, we'll use the ``from session variable`` option and configure the ``user_id`` column to be
|
|
automatically populated based on the value of the Authorization header ``X-Hasura-User-Id``.
|
|
|
|
Step 2: Run an insert mutation
|
|
------------------------------
|
|
|
|
Head to the GraphiQL interface in the console and try making an insert mutation on the ``article`` table with the
|
|
following headers (*to run through this example, don't forget to also grant the* ``user`` *role sufficient permissions
|
|
to select from the* ``article`` *table*):
|
|
|
|
- ``X-Hasura-role`` --> ``user`` (*to test the behaviour for the configured role*)
|
|
- ``X-Hasura-User-Id`` --> ``1`` (*this is the value we should expect in the* ``user_id`` *field*)
|
|
|
|
As mentioned earlier, you'll notice when you add the ``X-Hasura-role`` header that the field, ``user_id``, is no longer
|
|
available as the mutation type's field:
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/column-preset-schema-change-for-role.png
|
|
|
|
Now, if we run the following insert mutation, we'll see that the ``user_id`` field is indeed being set with the value
|
|
passed in the ``X-Hasura-User-Id`` header:
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/column-preset-mutation-result.png
|
|
|
|
.. note::
|
|
|
|
Not passing the configured header will result in a run-time error:
|
|
|
|
.. code-block:: JSON
|
|
|
|
{
|
|
"errors": [
|
|
{
|
|
"path": "$",
|
|
"error": "\"x-hasura-user-id\" header is expected but not found",
|
|
"code": "not-found"
|
|
}
|
|
]
|
|
}
|
|
|
|
|
|
Also see
|
|
--------
|
|
|
|
- :doc:`postgres-defaults`
|
|
- :doc:`sql-functions`
|