Skip to content
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.

Improve the multi-client implementation #97

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

thedadams
Copy link
Contributor

The first iteration of the multi-client had two issues that are fixed in these changes:

  1. The name SpecialConfigs was bad and has been renamed to APIGroupConfigs.
  2. The scheme that was built out of the various clients wouldn't have worked in certain scenarios. These changes require the caller to pass a scheme that will work.

The first iteration of the multi-client had two issues that are fixed in
these changes:

1. The name SpecialConfigs was bad and has been renamed to
APIGroupConfigs.
2. The scheme that was built out of the various clients wouldn't have
worked in certain scenarios. These changes require the caller to pass a
scheme that will work.

Signed-off-by: Donnie Adams <donnie@acorn.io>
@@ -149,6 +149,9 @@ func (c *cacheClient) List(ctx context.Context, list kclient.ObjectList, opts ..
}

func (c *cacheClient) Create(ctx context.Context, obj kclient.Object, opts ...kclient.CreateOption) error {
if u, ok := obj.(*uncached.Holder); ok {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the context for this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It allows controllers to create, update, and delete resources without watching the GVK. That is, I want to delete an object without creating a trigger in baaah.

@ibuildthecloud ibuildthecloud merged commit 6807d93 into acorn-io:main Aug 1, 2023
2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants