Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Landscape: I have two projects that are versioned in separate GitHub repositories (Project A & B). Project A is pointing to branch "mvp-development" and Project B is pointing to branch "mvp-development-source".
Use-Case: I want to use a storage task from Project A as a source for a transform task in Project B.
Issue: When selecting a source for the transform task in Project B, I select Project B in the "Projects" drop down but then the "Data Task" drop down is greyed out (see screenshot).
When testing this with another set of projects not versioned by GitHub this functionality works without issue. The transform task can clearly see the storage and transform objects from the other project.
I then tried to merge my changes for branch "mvp-development" in Project A to the main branch via a pull request. I then set Project A to point to the "main" branch in QDI and pulled down the remote changes (post merging of the pull request in GitHub) and voila! The storage tasks are now available to pull into Project B.
From the above experiment I can conclude that tasks can only be referenced from other projects if they belong to the main branch of the project. If this is the intended functionality of cross-project dependencies then this not a bug report but a feature request. However, I feel that this is unexpected behavior and should be resolved as in the QDI help docs this pattern of feature branch = development and main = production is directly referenced in the best practices for creating environments and branching strategies. Without the ability to reference a project in it's current state (outside of the main branch) we cannot actually develop the whole pipeline in a lower environment.
