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

feat: allow scope in relationship selector #735

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

adityathebe
Copy link
Member

@adityathebe adityathebe commented Jul 11, 2024

Allow specifying scope (scraper ID) in transform.relationships.
If no scope is specified, we default to using the scraper_id of the config that's searching for related configs.

@adityathebe adityathebe force-pushed the feat/scope-in-resource-selector branch from 0508059 to 62bafdc Compare July 11, 2024 14:36
@adityathebe adityathebe force-pushed the feat/scope-in-resource-selector branch from 62bafdc to 2d3889c Compare July 11, 2024 14:37
@adityathebe adityathebe marked this pull request as ready for review July 11, 2024 14:38
@adityathebe adityathebe requested a review from moshloop July 11, 2024 14:43
@moshloop moshloop merged commit 1051ae0 into main Jul 11, 2024
7 checks passed
@moshloop moshloop deleted the feat/scope-in-resource-selector branch July 11, 2024 15:06
Copy link

🎉 This PR is included in version 0.0.388 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants