Exposing the current recipe name as (environmental) variable or via a function

[almereyda]

After reading the documentation and man page and searching issues and discussions for "expose recipe name variable" or "recipe name function", I am not sure if this use case would be supported by just already:

When running a recipe, I would like to pass to it the name of the currently selected recipe as a pre-existing variable, alas GitLab's predefined CI/CD variables, either in just or shell notation. That is to template different invocations of a run with its name.

This could be a function.

_a:
  echo "{{ recipe() }}"
  @mkdir "{{ recipe() }}"
  @touch "{{ recipe() }}/default.conf"
 
test: _a

live: _a

These issues seem related:

• Add optional architecture attribution to receipt attribute annotations #1642
• [feature] User-defined functions #1059
• Feature request: Enable setting Variables in a Recipe #1023

Would I just have to implement this via a similar shell-based workaround?

[laniakea64]

So to be clear, in your example, you're looking for just test to do

echo "test"
mkdir "test"
touch "test/default.conf"

and for just live to do

echo "live"
mkdir "live"
touch "live/default.conf"

I don't think this is currently possible - this would be the depending_recipe() function idea proposed in #2411 (comment)

As a workaround, you could pass a recipe parameter to _a:

_a recipe:
  echo "{{ recipe }}"
  @mkdir "{{ recipe }}"
  @touch "{{ recipe }}/default.conf"
 
test: (_a 'test')

live: (_a 'live')

[almereyda]

Thank you for the help, @laniakea64!

(OT: When you check the @almereyda profile, you'll see I'm from the same place.)

Indeed it hadn't occurred to me to wrap my head into this direction, but the parameter seems like a suitable workaround.

Looking forward to the emergence of depending_recipe() when due.