pulumi-kubernetes-kotlin/com.pulumi.kubernetes.meta.v1.kotlin.inputs/ObjectMetaArgsBuilder/managedFields

managedFields

@JvmName(name = "pejxntmbhmyrcwxu")
suspend fun managedFields(value: Output<List<ManagedFieldsEntryArgs>>)
@JvmName(name = "dmjjrifobbrlpduy")
suspend fun managedFields(value: List<ManagedFieldsEntryArgs>?)

Parameters

value

ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like "ci-cd". The set of fields is always in the version that the workflow used when modifying the object.

@JvmName(name = "enytmcscpbegtulq")
suspend fun managedFields(vararg values: Output<ManagedFieldsEntryArgs>)

@JvmName(name = "hlkjhwuvvxhnpapc")
suspend fun managedFields(values: List<Output<ManagedFieldsEntryArgs>>)
@JvmName(name = "pfropmoyahelbhof")
suspend fun managedFields(vararg values: ManagedFieldsEntryArgs)

Parameters

values

ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like "ci-cd". The set of fields is always in the version that the workflow used when modifying the object.

@JvmName(name = "cjrnrimnmahpstmb")
suspend fun managedFields(argument: List<suspend ManagedFieldsEntryArgsBuilder.() -> Unit>)
@JvmName(name = "pbthtvycapefuify")
suspend fun managedFields(vararg argument: suspend ManagedFieldsEntryArgsBuilder.() -> Unit)
@JvmName(name = "mjjpgptcvymdwimn")
suspend fun managedFields(argument: suspend ManagedFieldsEntryArgsBuilder.() -> Unit)

Parameters

argument

ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like "ci-cd". The set of fields is always in the version that the workflow used when modifying the object.