Application path with arguments

[isohedronpipeline]

I have my applications managed with rez. I’d like to launch the rez managed tools with the launcher.

e.g. rez env maya-2026 -- maya or /path/to/rez env maya-2026 -- maya

This does not work with the launcher. If, however, I make a bash script with the same command, it works fine, including showing the Ayon menu and allowing me to load assets, so the required environment is forward through just fine.

Is this something that can be supported?

Additionally, are there tokens that can be provided to the application string? such as {project} or {user} or other context keys that the launcher has access to at the time of launching an application?

Thanks!

Ben

[mustafa_jafar]

Hello,

Let me link a related topic.

Rez + Ayon

Hi, I’m not using OpenPype or Ayon yet but I’m browsing through the documentation in preparation for an eventual test drive. I noticed that the DCCs must be launched through the Ayon app that must be downloaded and installed locally on the desktop machines. This concept is not compatible with our current solution (Rez) and would complicate things considerably for us. I’m starting this topic in order to start a discussion around the possibility of adding support for Rez, to talk about how we ar…

[luke.whitehorn]

I currently use Rez by setting the application like this

Additionally, are there tokens that can be provided to the application string? such as {project} or {user} or other context keys that the launcher has access to at the time of launching an application?

I actually came here to post this exact question. I am trying to do a per-task override to get an extra Rez package included. I tried to use {root[work]}/{project[name]}/.rezconfig but the AYON variables are not expanded here.
I’m guessing that there’s a chicken-egg situation with the resolution of environment variables vs AYON paths? Or are they just not supported in environment variables?