Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for an execute operation that passes the client library as a callback parameter #230

Open
markpollack opened this issue Sep 11, 2017 · 0 comments
Assignees

Comments

@markpollack
Copy link
Contributor

When an operation against the deployer API is not sufficient to implement a use-case, having access to the underlying platform client library for a SPI provider simplifies the app's implementation, by not having to create another separate platform client instance.

The model in RabbitOperations can serve as a template, e.g.

<T> T execute(ClientCallback<T> action) 

Each SPI implementer can parameterize this method with the type of the platform client.

@markpollack markpollack added this to the 1.3.0.M1 milestone Sep 11, 2017
@sabbyanandan sabbyanandan removed this from the 1.3.0.M1 milestone Sep 13, 2017
corneil pushed a commit that referenced this issue Mar 22, 2023
Resolves #245
Resolves #188
Resolves #230

* Replace calls that warn about http connection leaks when querying
  non-existent resources
* Finish StatefulSet cleanup / remove KubernetesHttpClient
* Fix warnings
* Some cleanups along the way
corneil pushed a commit that referenced this issue Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants