bug: Having a relationship named pool
breaks GraphQL API
#4807
Labels
priority/2
This issue stalls work on the project or its dependents, it's a blocker for a release
type/bug
Something isn't working as expected
Milestone
Component
API Server / GraphQL
Infrahub version
1.0.0
Current Behavior
Using the name
pool
for a relationship in a node schema will cause a failure when executing a GraphQL query.Expected Behavior
There should not be any issues.
Steps to Reproduce
Additional Information
The failure is raised because of a dynamic lookup of a function based on its name, in this case the name will be
process_pool
.The functions is then called with the bad number of parameters.
The text was updated successfully, but these errors were encountered: