Skip to content

Conversation

@hongchaodeng
Copy link
Contributor

No description provided.

@hongchaodeng hongchaodeng changed the title api: framework api to register user business logic api: framework api to register user sync() func Feb 8, 2018
*/

// SyncCallback defines user business logic for when resource events are triggered.
type SyncCallback struct {
Copy link

Choose a reason for hiding this comment

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

as we discussed offline, sync should not be per resource based.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right.
What's your suggestion for users to define the resources they "care about"?
Maybe we can change RegisterSync(SyncBallback, ResourceTypesToWatch...)?

Copy link

Choose a reason for hiding this comment

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

We should generate a Sync function stub for users to fill in. Users do not need to register that func with us at all. User only need to tell the SDK what resources that are interested in. Probably call sdk.Watch(resourceX).

@hongchaodeng
Copy link
Contributor Author

@hasbro17 to take over the PR.

@hongchaodeng
Copy link
Contributor Author

Closing this due to staleness

shawn-hurley pushed a commit to shawn-hurley/operator-sdk that referenced this pull request Apr 23, 2019
…ove-proxy-unit-test

remove proxy test because it needs a cluster.
VenkatRamaraju referenced this pull request in VenkatRamaraju/operator-sdk Mar 17, 2022
…added bundle image in it and serve contents. (#6)

Signed-off-by: rashmigottipati <[email protected]>
VenkatRamaraju referenced this pull request in VenkatRamaraju/operator-sdk Mar 22, 2022
…added bundle image in it and serve contents. (#6)

Signed-off-by: rashmigottipati <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants