Is there a way other than looking at `.proto` definitions to see what values are generated at the server/db level (and therefore not clientside concerns)?

[jakedoublev]

There are some values that seem like they could always be sole concerns of the service/DB layer and not exposed to the clientside, like resourceVersion (auto-incrementing?) and fqn that are now part of at least attribute management calls.

If there are indeed values that are created or accessed purely within the services that shouldn't be passed in Creates/Updates by Clients, is there an easier way to tell than looking at what types are strictly required within the .proto definitions? It seems like there will also be edge cases for optional field zero values that we'll need to handle carefully.

[strantalis]

I need to do some research but we might be able to leverage these options in the proto definitions to make things clearer.

https://github.com/googleapis/googleapis/blob/master/google/api/field_behavior.proto

Also I think we need to talk about the use of version. If we don't have intentions to keep track policy config history( which adds complexity) then we should just remove that field for now imo.

[jrschumacher]

Closing since #51 will resolve this. Reopen as needed.