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

feature: Add convert_query_response to Python Transforms #281

Open
FragmentedPacket opened this issue Feb 23, 2025 · 0 comments
Open

feature: Add convert_query_response to Python Transforms #281

FragmentedPacket opened this issue Feb 23, 2025 · 0 comments
Labels
priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release state/need-triage This issue needs to be triaged type/feature New feature or request

Comments

@FragmentedPacket
Copy link
Contributor

Component

infrahubctl CLI, Python SDK

Describe the Feature Request

Allow the same functionality of converting the GraphQL response into InfrahubNode objects for Python transformations.

Describe the Use Case

We fetch device IDs in our GraphQL query for the transform and would like to fetch those devices later on in the transform by using the Infrahub store that holds the objects from the query in the store to be retrieved later. This allows us to not have to run further queries to get the device information within the Python transform.

Additional Information

No response

@FragmentedPacket FragmentedPacket added the type/feature New feature or request label Feb 23, 2025
@exalate-issue-sync exalate-issue-sync bot added state/need-triage This issue needs to be triaged priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release labels Feb 25, 2025
@FragmentedPacket FragmentedPacket changed the title feature: Add convert_graphql_response to Python Transforms feature: Add convert_query_response to Python Transforms Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release state/need-triage This issue needs to be triaged type/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant