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

Get referenced obj using dynamic GVK API Rebased #7

Closed
wants to merge 15 commits into from

Conversation

rusty-jules
Copy link
Owner

Continuation of #1 opened by @nitishm

  • Get the referenced object using its GVK attributes
  • Convert to duckv1.AddressableType and get URL from status

nitishm and others added 9 commits October 25, 2022 02:46
The spec allows for sink parameters to specify both a ref and a uri. In
that case, the uri must be a path that is set on the resolved ref url.
Only if no ref is specified must the uri be an absolute url.

This makes the url type too strict for this field since url must always
be absolute.
@rusty-jules
Copy link
Owner Author

Still trying to figure out the right api for AddressableType. It feels odd right now to have essentially an abstract class since all of the methods of the type take DynamicObject as the receiver. A TryFrom<DynamicObject> doesn't work right now because it needs to be async in order to pull the k8s Config in the case that it's a Service. We could make that call blocking, but so far we have remained async runtime agnostic which is a good thing.

@rusty-jules rusty-jules deleted the feat/kref-uri-resolver-impl-rebase branch February 12, 2024 09:18
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