Hi again! Is there any way to manage

[potent portal]

Hi @lean pelican, does partial schema update help on this https://docs.permify.co/operations/partial-schema-update ?

Regarding the schema changes, one of the best practise to manage the changes is setting up a central git repository that stores the schema YAML file. This way, you can centrally check and approve every schema change before deploying it.

In Permify Cloud we even streamline this management process for you with connecting your GitHub. Basically you can automatically deploy authorization models to Permify directly from your GitHub repository.

I don't know is this relevant but these are the approaches we currently have to streamline the schema changes. Would love to hear your input.

[lean pelican]

I read about it in the documentation but it doesn't allow to create or delete entities, only to update the existing ones

[potent portal]

If the schema update had that functionality (delete/create entities), would it help you achieve what you want?

[lean pelican]

Yes, I think it would be great and would give much more flexibility in modifying the authorization model using only code

[potent portal]

Great

[potent portal]

My latest message won't delivered for some reason, so I will discuss about adding delete/create entity functionality with the team and get circle back to you on this.

[lean pelican]

Thank you 🙂

[potent portal]

Hi @lean pelican, hope all is well

I've discussed this with the engineering team and they said it should include create/delete entity. If you're having problem with that its a bug. Could you try again or elaborate more on why you can't create/delete entities with the https://docs.permify.co/api-reference/schema/partial-write