We have orchestrator host and tenant and since us developper can’t have access to orchestrator host, is it better to upload all dependencies on orchestrator host or should we stick to important dependencies in host and not important one to tenant ? Or should we create a share folder with all dependencies in it ?
Hi @Maximilien_Selva
Use Host for: Core/standard dependencies used across tenants (maintained by platform admin).
Use Tenant for: All other project-specific or non-critical dependencies (developer-accessible).
Avoid shared folder unless you have specific edge cases or sandbox environments.
Hope this works!
Ideally storing at tenant level makes sense for our own packages..
So the basic difference is host level packages are accessible across trnants so in a case when there is dev uat and prod trnants in same org..then or hestrator host shows all packages across tenants
But while moving from one to another env..we need to have some guardrails which can be implemented using tenant level feed and also to test and then deploy its better to tenant level feed itself
Unless you are on on prem setup with different orgs for each dev uat and prod …orchestrator host level would not make sense
Hope this helps
Cheers
Hey @Maximilien_Selva In general, use the Orchestrator’s Package Feed for managing dependencies, which simplifies the process of version control and deployment, allowing robots to access dependencies as needed without direct involvement with the host machine.
For runtime dependencies those directly required by your process at execution time, upload them to the host.
For shared or reusable dependencies e.g., libraries, keep them in the tenant via the Orchestrator Package Feed.
Ensure that the correct versions of dependencies are locked within your project.json to avoid version conflicts.
cheers