We use mage for a few projects, and noticed a minor discovery problem of the aliases we setup for our targets. While yes you can run mage -h target to see aliases, that's not an obvious command to know about.
I have added the output of Aliases and to what targetname they point to in the mage -l output. That way it is more easily discoverable.
If there are no aliases setup, the Aliases section won't show up. I used an actual go if block instead of as a template one as it made err variable management a bit simpler. But I can make adjustments if it is preferred.
No new tests were added as a bunch of existing tests would fail if Aliases always showed up, and the ImportLists test fails if it doesn't show up.
We use mage for a few projects, and noticed a minor discovery problem of the aliases we setup for our targets. While yes you can run
mage -h targetto see aliases, that's not an obvious command to know about.I have added the output of Aliases and to what targetname they point to in the
mage -loutput. That way it is more easily discoverable.If there are no aliases setup, the Aliases section won't show up. I used an actual go if block instead of as a template one as it made
errvariable management a bit simpler. But I can make adjustments if it is preferred.No new tests were added as a bunch of existing tests would fail if
Aliasesalways showed up, and the ImportLists test fails if it doesn't show up.I can add additional tests if requested though.