Skip to content

Latest commit

 

History

History
17 lines (13 loc) · 1.97 KB

V1ManagedFieldsEntry.md

File metadata and controls

17 lines (13 loc) · 1.97 KB

V1ManagedFieldsEntry

ManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.

Properties

Name Type Description Notes
api_version str APIVersion defines the version of this resource that this field set applies to. The format is "group/version" just like the top-level APIVersion field. It is necessary to track the version of a field set because it cannot be automatically converted. [optional]
fields_type str FieldsType is the discriminator for the different fields format and version. There is currently only one possible value: "FieldsV1" [optional]
fields_v1 object FieldsV1 holds the first JSON version format as described in the "FieldsV1" type. [optional]
manager str Manager is an identifier of the workflow managing these fields. [optional]
operation str Operation is the type of operation which lead to this ManagedFieldsEntry being created. The only valid values for this field are 'Apply' and 'Update'. [optional]
subresource str Subresource is the name of the subresource used to update that object, or empty string if the object was updated through the main resource. The value of this field is used to distinguish between managers, even if they share the same name. For example, a status update will be distinct from a regular update using the same manager name. Note that the APIVersion field is not related to the Subresource field and it always corresponds to the version of the main resource. [optional]
time datetime Time is timestamp of when these fields were set. It should always be empty if Operation is 'Apply' [optional]

[Back to Model list] [Back to API list] [Back to README]