fast-vr-44972
02/18/2025, 9:36 AMproject
and branch
in metaflow. For more context, we access artifact generated by flow run of A in another flow B.
Usually this works fine unless we want to experiment with B having a new branch. If I do nothing, I get error which I guess is because by default it's trying to use the production namespace. How can we handle it so that for new branch, it will either try to look it up in the branch specific namespace or I can do some error handling and just ignore this and use a default value of artifact from A.
Object not in the current namespace:
victorious-lawyer-58417
02/18/2025, 8:13 PM@project
creates a branch-specific tag and a corresponding namespace and limits visibility to objects in that scope, which is why you can't access artifacts across branches by default (by design)victorious-lawyer-58417
02/18/2025, 8:14 PM@project
creates a project-level tag of the format, project:PROJECT_NAME
which covers all branches in that project
hence you can switch to that namespace by doing
namespace(f'project:{current.project_name}')
...after which you can access runs and artifacts across all branches in that projectvictorious-lawyer-58417
02/18/2025, 8:14 PMvictorious-lawyer-58417
02/18/2025, 8:16 PM