NodeManager.query supports a parameter called branch_agnostic that lets you query for nodes across branches but if you query on the main branch all Node objects returned will be associated with the main branch instead of the actual branch where the object is created.
I.e. https://github.com/opsmill/infrahub/blob/develop/backend/infrahub/core/manager.py#L893
Expected Behavior
each node returned in a query should have the correct branch associated with it
Steps to Reproduce
I don't think this can be reproduced outside of a unit test right now
Component
API Server / GraphQL
Current Behavior
from @ogenstad in Slack
NodeManager.querysupports a parameter calledbranch_agnosticthat lets you query for nodes across branches but if you query on the main branch all Node objects returned will be associated with the main branch instead of the actual branch where the object is created. I.e. https://github.com/opsmill/infrahub/blob/develop/backend/infrahub/core/manager.py#L893Expected Behavior
each node returned in a query should have the correct
branchassociated with itSteps to Reproduce
I don't think this can be reproduced outside of a unit test right now
Additional Information
No response