I created a service and it is successful. Later, user comes back and tries to change a leaf “tenantName”, I should not allow the user to change this leaf once it is set.
I thought of using opaque object for this purpose.
Any suggestions ?
If the service is modelled as a list, would it work if “tenantName” is made part of the key? Would that satisfy the requirement?
Thanks for input. But we are not allowed to make it as key.
With regards Jaswanth
Usually a thing like this would be handled by an access control rule, allowing some certain group of users to create but not update.
To make the system fundamentally reject changes to specific leaves sounds like a really bad idea. Such a "feature" could for example make it difficult to restore a backup.