bug: Users should not be given the option to add enums to restricted namespaces

[ogenstad]

Component

Frontend UI

Infrahub version

v1.0.0-dev0

Current Behavior

When a user visits an object that has an enum they are given the option to add or remove options. However this shouldn't be allowed if the user comes from a restricted namespace such as "Core"

Here is an example of "CoreObjectPermission":

The "Add Option" button should not be there for restricted namespaces.

If the user tries to add something an error is returned from the backend:

Expected Behavior

This action should not be presented for users for objects in a restricted namespace. The frontend can see this information within the schema.

Steps to Reproduce

1 Go to the Permissions
2. Edit a CoreObjectPermission
3. Select "actions"
4. Note that "Add option" is available

Additional Information

No response

[bilalabbad]

Hey thanks for the details. With schema endpoint /api/schema, we have access to namespace data like:

  "namespaces": [
    {
      "name": "Core",
      "user_editable": false
    },
    {
      "name": "Builtin",
      "user_editable": true
    },
    ...

What you call restricted namespace are namespace with "user_editable": false right?

[dgarros]

Ideally I think we should fix this issue with the new permissions metadata at the attribute level
this way the frontend doesn't have to do anything special