golang-k8s-sigs-structured-merge-diff 4.0.2+ds1-2 source package in Ubuntu

Changelog

golang-k8s-sigs-structured-merge-diff (4.0.2+ds1-2) unstable; urgency=medium

  * Team upload
  * Upload to unstable

 -- Reinhard Tartler <email address hidden>  Fri, 27 Nov 2020 13:49:28 -0500

Upload details

Uploaded by:
Debian Go Packaging Team
Uploaded to:
Sid
Original maintainer:
Debian Go Packaging Team
Architectures:
all
Section:
golang
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Hirsute: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
golang-k8s-sigs-structured-merge-diff_4.0.2+ds1-2.dsc 2.6 KiB ebb0b6ed36bef078baf222ec7f698894d0363e517f765e5b00943e02846ee451
golang-k8s-sigs-structured-merge-diff_4.0.2+ds1.orig.tar.xz 114.3 KiB 5502f1b6b65397e5ea27a77a9885dac76a3b4de2ef5f6354bc148052a8104db3
golang-k8s-sigs-structured-merge-diff_4.0.2+ds1-2.debian.tar.xz 3.2 KiB 485ca35d006d7b2726166eef1a6d4a18ca458ee5e996cd76f9c0fd786fe89e1f

Available diffs

No changes file available.

Binary packages built by this source

golang-k8s-sigs-structured-merge-diff-dev: implementation for "server-side apply" (library)

 What is the apply operation?
 .
 It models resources in a control plane as having multiple
 "managers". Each manager is typically trying to manage only one
 aspect of a resource. The goal is to make it easy for disparate
 managers to make the changes they need without messing up the things
 that other managers are doing. In this system, both humans and
 machines (aka "controllers") act as managers.
 .
 To do this, it explicitly tracks (using the fieldset data structure)
 which fields each manager is currently managing.
 .
 Now, there are two basic mechanisms by which one modifies an object.
 .
 PUT/PATCH: This is a write command that says: "Make the object look
 EXACTLY like X".
 .
 APPLY: This is a write command that says: "The fields I manage should
 now look exactly like this (but I don't care about other fields)".
 .
 For PUT/PATCH, it deduces which fields will be managed based on what
 is changing. For APPLY, the user is explicitly stating which fields
 they wish to manage (and therefore requesting deletion of any fields
 that they used to manage but stop mentioning).
 .
 Any time a manager begins managing some new field, that field is removed
 from all other managers. If the manager is using the APPLY command, it
 calls these conflicts, and will not proceed unless the user passes the
 "force" option. This prevents accidentally setting fields which some
 other entity is managing.
 .
 PUT/PATCH always "force". They are mostly used by automated systems,
 which won't do anything productive with a new error type.