creating permission through the API leaves metadata inconsistent

Adding a permission to a computed field through the API leaves the metadata inconsistent

Since there is no way right now to add a computed filed permission through the console, I’m using the create_select_permission API to add the permission to the table.

Here’s the request to add permission

{
    "type" : "create_select_permission",
    "args" : {
        "table" : "clients",
        "role" : "user",
        "permission" : {
            "columns" : ["description", "id", "logo_url", "name", "website_url"],
            "filter" : {
                "users" : {"id":{"_eq":"X-Hasura-User-Id"}}
            },
            "computed_fields": ["sections"]
        }
    }
}

After this, everything works fine. But when I restart the console, I get the inconsistent metadata error. Then I try to remove the permission through the API and I get this error request

{
    "type" : "drop_select_permission",
    "args" : {
        "table" : "clients",
        "role" : "user"
    }
}

response

{
    "path": "$.args",
    "error": "select permission on \"clients\" for role \"user\" does not exist",
    "code": "permission-denied"
}

In order to get everything work again, I have to manually delete the permission from the DB and then add it again using the API

[rakeshkky]

@tafelito Great to know that. Thank you 🙂. Closing the issue now.

[tafelito]

@rakeshkky I just updated to beta.10 and it’s working now and I didn’t have to manually add the computed field through the API

Thanks for the quick response!