Interface FieldBehaviorValueMembers

Represents the FIELD_BEHAVIOR_UNSPECIFIED protobuf enum value.

Indicates field is a resource ID, so it MUST be present on a resource update, but MUST NOT be set on create. Otherwise, RPC will fail with the INVALID_ARGUMENT error

This indicates that the field can't be changed during a resource update. Changing the field value will cause an INVALID_ARGUMENT error. For message fields, this applies to the field itself. Nested immutable fields do not make a mutable parent message immutable, and such a parent message may still be cleared. Resource recreate requires a change of the field value.

Indicates field is not present in output.

Indicates that an empty message and a null have different semantics. Usually, that field is a feature spec message: its empty message enables that feature, and null disables it. Such a message is different from bool because it already has some feature parameters, or they can be added later in a backward-compatible way. IMPORTANT: if the message itself is recursive, this behavior is forced.

Indicates that an empty (default) value will be filled by the server. Usually, that field is a feature spec value, which by default is computed. Values marked with this annotation won't raise error if they are not set and the returned value is not equal to protobuf default.

IMPORTANT: Updating this value from explicit to default may not lead to Update call in some tools (eg Terraform). Compound values (messages, lists and maps) may result in unpredictable updates (see examples in guidelines).

Indicates field can't be set on create or changed on update. Otherwise, RPC will fail with the INVALID_ARGUMENT error

The same as OUTPUT_ONLY