fix(deps): update non-minor dependencies #113

renovate · 2024-10-21T09:03:28Z

This PR contains the following updates:

Package	Type	Update	Change
docker.io/bitnami/kubectl (source)		patch	`1.32.0-debian-12-r0` -> `1.32.1-debian-12-r5`
docker.io/bitnami/os-shell (source)		patch	`12-debian-12-r31` -> `12-debian-12-r36`
github.com/onsi/ginkgo/v2	require	patch	`v2.22.0` -> `v2.22.2`
github.com/onsi/gomega	require	patch	`v1.36.0` -> `v1.36.2`
github.com/sap/admission-webhook-runtime	require	patch	`v0.1.44` -> `v0.1.57`
github.com/sap/component-operator-runtime	require	patch	`v0.3.45` -> `v0.3.69`
github.com/sap/go-generics	require	patch	`v0.2.20` -> `v0.2.26`
go (source)	golang	patch	`1.23.2` -> `1.23.6`
golang	stage	patch	`1.23.4` -> `1.23.6`
k8s.io/api	require	patch	`v0.32.0` -> `v0.32.1`
k8s.io/apiextensions-apiserver	require	patch	`v0.32.0` -> `v0.32.1`
k8s.io/apimachinery	require	patch	`v0.32.0` -> `v0.32.1`
k8s.io/client-go	require	patch	`v0.32.0` -> `v0.32.1`
k8s.io/code-generator	require	patch	`v0.32.0` -> `v0.32.1`
k8s.io/kube-aggregator	require	patch	`v0.32.0` -> `v0.32.1`
sigs.k8s.io/controller-runtime/tools/setup-envtest	require	digest	`a9b7c2d` -> `2e8ba92`

Release Notes

onsi/ginkgo (github.com/onsi/ginkgo/v2)

`v2.22.2`

Compare Source

What's Changed

Bump golang.org/x/net from 0.32.0 to 0.33.0 by @dependabot in https://github.com/onsi/ginkgo/pull/1496
Bump golang.org/x/crypto from 0.17.0 to 0.31.0 in /ginkgo/performance/_fixtures/performance_fixture by @dependabot in https://github.com/onsi/ginkgo/pull/1498
Bump github.com/onsi/gomega from 1.36.1 to 1.36.2 by @dependabot in https://github.com/onsi/ginkgo/pull/1499

Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2

`v2.22.1`

Compare Source

2.22.1

Fixes

Fix CSV encoding

Update tests [aab3da6]
Properly encode CSV rows [c09df39]
Add test case for proper csv escaping [96a80fc]
Add meta-test [43dad69]

Maintenance

ensure *.test files are gitignored so we don't accidentally commit compiled tests again [c88c634]
remove golang.org/x/net/context in favour of stdlib context [4df44bf]

onsi/gomega (github.com/onsi/gomega)

`v1.36.2`

Compare Source

Maintenance

Bump nokogiri from 1.16.3 to 1.16.5 in /docs by @dependabot in https://github.com/onsi/gomega/pull/757
Bump github.com/onsi/ginkgo/v2 from 2.20.1 to 2.22.1 by @dependabot in https://github.com/onsi/gomega/pull/808
Bump golang.org/x/net from 0.30.0 to 0.33.0 by @dependabot in https://github.com/onsi/gomega/pull/807
Bump google.golang.org/protobuf from 1.35.1 to 1.36.1 by @dependabot in https://github.com/onsi/gomega/pull/810

`v1.36.1`

Compare Source

1.36.1

Fixes

Fix https://github.com/onsi/gomega/issues/803 [1c6c112]
resolves #696: make HaveField great on pointer receivers given only a non-addressable value [4feb9d7]

sap/admission-webhook-runtime (github.com/sap/admission-webhook-runtime)

sap/component-operator-runtime (github.com/sap/component-operator-runtime)

`v0.3.69`

Compare Source

Enhancements

Starting with this release, the deletion of dependent objects will fail unless the existing value of the owner-id label of the dependent object matches the component that wants to delete it. If the owner-id label is missing, or the value does not match, the deletion will be rejected.

`v0.3.68`

Compare Source

`v0.3.67`

Compare Source

(Potentially) incompatible changes

The type reconciler.ReconcilerOptions is changed:
- The boolean attribute CreateMissingNamespaces is replaced with a new attribute MissingNamespacesPolicy that can have the values Create (default) or DoNotCreate. The default behavior is backwards compatible; only people who explicitly have set the old attribute have to adopt the new notation in the obvious way.
- Finalizer and field owner used by the reconciler can now explicitly be configured by setting the attributes Finalizer and FieldOwner in the reconciler options. If unset it defaults to the reconciler name passed to reconciler.NewReconciler(), which makes that change backwards compatible.
The interface component.PolicyConfiguration was enhanced by an additional method GetMissingNamespacesPolicy() reconciler.MissingNamespacesPolicy. People who implemented that interface explicitly have to add this method to their implementation. Most people however probably just include component.PolicySpec into their component's spec type. They don't have to react, but should regenerate their CRD manifest, in order to expose the new field spec.missingNamespacesPolicy which is now contained in component.PolicySpec.
The type component.ReconcilerOptions is changed in a way similar to reconciler.ReconcilerOptions (that is, the attribute CreateMissingNamespaces is replaced by MissingNamespacesPolicy and new attributes Finalizer and FieldOwner are added). In addition, there is a new option DefaultServiceAccount which allows the name of a service account that can be used during the reconciliation of a component to impersonate the client used to reconcile the dependent objects, as long as the component does not explicitly specify an impersonation or kubeconfig (by implementing the ImpersonationConfiguration or ClientConfiguration interfaces); note that the specified DefaultServiceAccount always refers to the metadata.namespace or the component.
When a component resource is reconciled, two Kubernetes API clients are constructed:
- The local client; it always points to the cluster where the component resides. If the component implements impersonation (that is, the component type or its spec implements the ImpersonationConfiguration interface), and an impersonation user or groups are specified by the component resource, then the specified user and groups are used to impersonate the controller's kubeconfig. Otherwise, if a DefaultServiceAccount is defined in the reconciler's options, then that service account (relative to the components metadata.namespace ) is used to impersonate the controller's kubeconfig. Otherwise, the controller's kubeconfig itself is used to build the local client. The local client is passed to generators via their context. For example, the HelmGenerator and KustomizeGenerator provided by component-operator-runtime use the local client to realize the localLookup and mustLocalLookup template functions.
- The target client; if the component specifies a kubeconfig (by implementing the ClientConfiguration interface), then that kubeconfig is used to build the target client. Otherwise, a local client is used (possibly impersonated), created according the the logic described above. The target client is used to manage dependent objects, and is passed to generators via their context. For example, the HelmGenerator and KustomizeGenerator provided by component-operator-runtime use the target client to realize the lookup and mustLookup template functions.
This changes the previous impersonation logic a little bit. Other than before, no impersonation happens at all if a kubeconfig is specified (through ClientConfiguration). In addition, relative service accounts returned by GetImpersonationUser() (that is: a user of the form system:serviceaccounts::name, setting an empty namespace), now will be interpreted always relative to the metadata.namespace of the component resource; previously, the namespace specified by a PlacementConfiguration implementation was considered as well; this is no longer the case.
The clnt parameter of the HelmGenerator and KustomizeGenerator constructors is now ignored (and will be removed in a future release). Instead, these generators always use the local client, constructed as described above.

`v0.3.66`

Compare Source

`v0.3.65`

Compare Source

`v0.3.64`

Compare Source

`v0.3.63`

Compare Source

`v0.3.62`

Compare Source

Incompatible changes

Previously, the forced re-apply of dependent objects was based on a timestamp that was coded into the object digest. As a consequence, the digest annotation of every dependent object was updated more or less every 60 minutes. Which caused problems (e.g. with crossplane).

From this release onwards, the force-re-apply mechanism is based on the new status field status.inventory[].lastAppliedAt.

Note: YOU MUST, REALLY MUST, regenerate your component CRD when using a version of component-operator-runtime containing this release, and ship the module update together with the updated CRD!!!

`v0.3.61`

Compare Source

`v0.3.60`

Compare Source

`v0.3.59`

Compare Source

This release is non-functional (preparation for future work). It ships a new status field .status.inventory[].lastAppliedAt.

`v0.3.58`

Compare Source

This release is a bugfix release for the clm cli. So far, while applying or deleting a release, clm was aborting immediately if an error occurred. This is not very convenient. At least in some ephemeral error situations, it should behave in a more resilient way. So, with this release, clm tries to recognise such ephemeral errors (for example 409 - Conflict responses from the API server), and retries the failing operation a couple of times.

`v0.3.57`

Compare Source

`v0.3.56`

Compare Source

Enhancements

A new flag --create-namespace was added to clm apply. If specified the specified release namespace will be auto-created if missing. Note that in that case, the namespace is not part of the release inventory. In particular, it will not be deleted if the component gets deleted.

`v0.3.55`

Compare Source

This release adds a new interface PolicyConfiguration that component types (or their spec types) can implement:

type PolicyConfiguration interface {
  // Get adoption policy.
  // Must return a valid AdoptionPolicy, or the empty string (then the reconciler/framework default applies).
  GetAdoptionPolicy() reconciler.AdoptionPolicy
  // Get update policy.
  // Must return a valid UpdatePolicy, or the empty string (then the reconciler/framework default applies).
  GetUpdatePolicy() reconciler.UpdatePolicy
  // Get delete policy.
  // Must return a valid DeletePolicy, or the empty string (then the reconciler/framework default applies).
  GetDeletePolicy() reconciler.DeletePolicy
}

Through this interface, components can override the framework default policies that would otherwise apply. Of course, dependent resources can still override the behaviour using the well-known annotations. For easier consumption (similar to the already existing Configuration interfaces), there is a standard implementation PolicySpec that components may embed into their spec).

Furthermore, the semantics of the deletion policy was slightly changed:

Other than before, the deletion policy is now ignored during apply. That is, if an existing object becomes obsolete while applying a new revision of the depdendents' manifests, it will be always deleted now, even if it has an effective deletion policy 'orphan'. In other words, the deletion policy will only be honoured if the owning component itself is deleted.
So far, a component's deletion will block if it contains extension types, and there exist any foreign instances of these types in the cluster; this check will now be skipped if all dependents of the component have an effective deletion policy 'orphan'.

`v0.3.54`

Compare Source

This release adds some new template functions to HelmGenerator and KustomizeGenerator.

Template functions for bitwise operations:
- func bitwiseShiftLeft(by any, arg any) (uint64, error)
- func bitwiseShiftRight(by any, arg any) (uint64, error)
- func bitwiseAnd(args ...any) (uint64, error)
- func bitwiseOr(args ...any) (uint64, error)
- func bitwiseXor(args ...any) (uint64, error)
Functions for IPv4 address handling:
- func parseIPv4Address(data any) (uint32, error)
- func formatIPv4Address(data any) (string, error)

`v0.3.53`

Compare Source

`v0.3.52`

Compare Source

This is a bugfix release, but it slightly changes the procedure how dependent objects are reconciled. In detail:

Until now, reconciler.Apply() (which is what happens if a component is reconciled, not deleted) first deleted all redundant objects, that is objects which appear in the component's inventory, but are no longer part of the current manifest list. Only after all redundant objects were gone, the reconciliation of the current dependents was started. This potentially caused some deadlock situations, e.g. in component-operator. To overcome, the deletion part was shifted to the end of
reconciler.Apply(), after the application of the current manifest list. This should not be a noticeable change. However, the completion handling still happens early (before the reconciliation of the dependents), and was slightly changed as well; for example, object deletions happening as consequence of a completion now no longer honour delete-order or delete-policy.

`v0.3.51`

Compare Source

`v0.3.50`

Compare Source

`v0.3.49`

Compare Source

`v0.3.48`

Compare Source

`v0.3.47`

Compare Source

`v0.3.46`

Compare Source

sap/go-generics (github.com/sap/go-generics)

`v0.2.26`

Compare Source

`v0.2.25`

Compare Source

`v0.2.24`

Compare Source

`v0.2.23`

Compare Source

`v0.2.22`

Compare Source

`v0.2.21`

Compare Source

golang/go (go)

`v1.23.6`

`v1.23.5`

`v1.23.4`

`v1.23.3`

kubernetes/api (k8s.io/api)

`v0.32.1`

Compare Source

kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)

`v0.32.1`

Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)

`v0.32.1`

Compare Source

kubernetes/client-go (k8s.io/client-go)

`v0.32.1`

Compare Source

kubernetes/code-generator (k8s.io/code-generator)

`v0.32.1`

Compare Source

kubernetes/kube-aggregator (k8s.io/kube-aggregator)

`v0.32.1`

Compare Source

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2024-10-21T09:03:29Z

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

17 additional dependencies were updated

Details:

Package	Change
`sigs.k8s.io/controller-runtime`	`v0.19.3` -> `v0.20.1`
`github.com/google/gnostic-models`	`v0.6.8` -> `v0.6.9`
`github.com/google/pprof`	`v0.0.0-20241029153458-d1b30febd7db` -> `v0.0.0-20241210010833-40e02aabc2ad`
`github.com/prometheus/client_golang`	`v1.20.4` -> `v1.20.5`
`github.com/spf13/afero`	`v1.6.0` -> `v1.12.0`
`github.com/spf13/cast`	`v1.7.0` -> `v1.7.1`
`github.com/spf13/pflag`	`v1.0.5` -> `v1.0.6`
`golang.org/x/crypto`	`v0.31.0` -> `v0.32.0`
`golang.org/x/net`	`v0.30.0` -> `v0.33.0`
`golang.org/x/oauth2`	`v0.23.0` -> `v0.25.0`
`golang.org/x/sys`	`v0.28.0` -> `v0.29.0`
`golang.org/x/term`	`v0.27.0` -> `v0.28.0`
`golang.org/x/time`	`v0.7.0` -> `v0.10.0`
`golang.org/x/tools`	`v0.26.0` -> `v0.28.0`
`google.golang.org/protobuf`	`v1.35.1` -> `v1.36.1`
`k8s.io/kube-openapi`	`v0.0.0-20241105132330-32ad38e42d3f` -> `v0.0.0-20241212222426-2c72e554b1e7`
`sigs.k8s.io/structured-merge-diff/v4`	`v4.4.2` -> `v4.5.0`

renovate · 2025-02-05T19:19:57Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

renovate bot added the dependencies label Oct 21, 2024

renovate bot changed the title ~~fix(deps): update module github.com/sap/component-operator-runtime to v0.3.46~~ fix(deps): update non-minor dependencies Oct 21, 2024

renovate bot force-pushed the renovate/non-minor-deps branch 3 times, most recently from 130a78e to c313f2f Compare October 23, 2024 22:20

renovate bot changed the title ~~fix(deps): update non-minor dependencies~~ chore(deps): update non-minor dependencies Oct 23, 2024

renovate bot force-pushed the renovate/non-minor-deps branch 8 times, most recently from fe6a807 to dc9c42b Compare October 30, 2024 22:37

renovate bot force-pushed the renovate/non-minor-deps branch 5 times, most recently from fa45f16 to d1476e9 Compare November 7, 2024 09:55

renovate bot force-pushed the renovate/non-minor-deps branch 4 times, most recently from 9c65b8c to 7889b67 Compare November 11, 2024 12:10

renovate bot force-pushed the renovate/non-minor-deps branch 6 times, most recently from 2b13e6d to d43bba8 Compare November 21, 2024 09:21

renovate bot force-pushed the renovate/non-minor-deps branch 10 times, most recently from 8a4285b to 1490d1a Compare January 23, 2025 01:46

renovate bot force-pushed the renovate/non-minor-deps branch 8 times, most recently from 48bbe9e to b7f23e0 Compare January 30, 2025 01:36

renovate bot force-pushed the renovate/non-minor-deps branch 6 times, most recently from c8183cd to 39fe33a Compare February 5, 2025 14:03

fix(deps): update non-minor dependencies

f2c3c81

renovate bot force-pushed the renovate/non-minor-deps branch from 39fe33a to f2c3c81 Compare February 5, 2025 18:30

update modules, make manifests

3734384

cbarbian-sap merged commit 261201f into main Feb 5, 2025
6 checks passed

cbarbian-sap deleted the renovate/non-minor-deps branch February 5, 2025 19:37

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update non-minor dependencies #113

fix(deps): update non-minor dependencies #113

renovate bot commented Oct 21, 2024 •

edited

Loading

renovate bot commented Oct 21, 2024 •

edited

Loading

renovate bot commented Feb 5, 2025

fix(deps): update non-minor dependencies #113

fix(deps): update non-minor dependencies #113

Conversation

renovate bot commented Oct 21, 2024 • edited Loading

Release Notes

What's Changed

2.22.1

Fixes

Maintenance

Maintenance

1.36.1

Fixes

Enhancements

(Potentially) incompatible changes

Incompatible changes

Enhancements

Configuration

renovate bot commented Oct 21, 2024 • edited Loading

ℹ Artifact update notice

File name: go.mod

renovate bot commented Feb 5, 2025

Edited/Blocked Notification

renovate bot commented Oct 21, 2024 •

edited

Loading

renovate bot commented Oct 21, 2024 •

edited

Loading