crypttab: removes jijna delimiters from example using when

[Akasurde]

SUMMARY

The current example includes extra jinja delimiters which
result in double-interpretation of the statement.

Fixes: #10078

Signed-off-by: Abhijeet Kasurde Akasurde@redhat.com

ISSUE TYPE

• Docs Pull Request

[ansibullbot]

cc @groks
click here for bot help

[patchback]

Backport to stable-8: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 1936fe5 on top of patchback/backports/stable-8/1936fe5181f970d18d24b6165165e854f3b30a77/pr-10079

Backporting merged PR #10079 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/community.general.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-8/1936fe5181f970d18d24b6165165e854f3b30a77/pr-10079 upstream/stable-8

4. Now, cherry-pick PR crypttab: removes jijna delimiters from example using when #10079 contents into that branch:

   $ git cherry-pick -x 1936fe5181f970d18d24b6165165e854f3b30a77

   If it'll yell at you with something like fatal: Commit 1936fe5181f970d18d24b6165165e854f3b30a77 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 1936fe5181f970d18d24b6165165e854f3b30a77

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR crypttab: removes jijna delimiters from example using when #10079 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-8/1936fe5181f970d18d24b6165165e854f3b30a77/pr-10079

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-9: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 1936fe5 on top of patchback/backports/stable-9/1936fe5181f970d18d24b6165165e854f3b30a77/pr-10079

Backporting merged PR #10079 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/community.general.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-9/1936fe5181f970d18d24b6165165e854f3b30a77/pr-10079 upstream/stable-9

4. Now, cherry-pick PR crypttab: removes jijna delimiters from example using when #10079 contents into that branch:

   $ git cherry-pick -x 1936fe5181f970d18d24b6165165e854f3b30a77

   If it'll yell at you with something like fatal: Commit 1936fe5181f970d18d24b6165165e854f3b30a77 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 1936fe5181f970d18d24b6165165e854f3b30a77

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR crypttab: removes jijna delimiters from example using when #10079 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-9/1936fe5181f970d18d24b6165165e854f3b30a77/pr-10079

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

@sivel thanks for reporting!
@Akasurde thanks for fixing!

[patchback]

Backport to stable-10: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-10/1936fe5181f970d18d24b6165165e854f3b30a77/pr-10079

Backported as #10080

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

Created manual backport to stable-9 in #10081.