You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However one might want to refer to the default variables section from other parts of the documentation. I thought that the unique section name debops.cryptsetup default variables could be used directly from other parts using the ref role but I just tried it with v1.4.6 and it seems that it is not possible. As documented for the ref role, sections should be referred to by label. I therefore would propose to add such a label by default which could look like this:
This makes the header kinda big... But I suppose that if there's no other way and the header doesn't work (any idea why?), then we could go with this solution.
I am not sure why it does not work. I thought that I had used something like this before but when I tried it was always kind of unreliable so a label would be best.
Ok, lets leave this issue open for now. I used the proposed label in https://github.com/debops/ansible-cryptsetup/pull/18 but until the need in other places arises we do not need to make this the default just yet.
Currently the header of
default/main.yml
files looks something like this:However one might want to refer to the default variables section from other parts of the documentation. I thought that the unique section name
debops.cryptsetup default variables
could be used directly from other parts using the ref role but I just tried it with v1.4.6 and it seems that it is not possible. As documented for the ref role, sections should be referred to by label. I therefore would propose to add such a label by default which could look like this:This allows to refer to the section like this:
Fortunately, that header update can easily by automated by yaml4rst and
debops-optimize
:)The text was updated successfully, but these errors were encountered: