Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

functional backport of 74448 #74567

Merged
merged 1 commit into from May 4, 2021

Conversation

acozine
Copy link
Contributor

@acozine acozine commented May 4, 2021

SUMMARY

#74448 won't backport cleanly because we are not backporting #74324.

Instead of wrestling with the merge conflict and trying to get this into a Docs Backportapalooza, we opened this PR as a functional backport of commit c63b867.

ISSUE TYPE
  • Docs Pull Request
COMPONENT NAME

docs.ansible.com

@acozine acozine added backport This PR does not target the devel branch. docs This issue/PR relates to or includes documentation. affects_2.11 labels May 4, 2021
@ansibot ansibot added core_review In order to be merged, this PR must follow the core review workflow. needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels May 4, 2021
@@ -278,7 +278,7 @@
# choice but to create world readable temporary files to execute a module on
# the remote machine. This option is False by default for security. Users may
# turn this on to have behaviour more like Ansible prior to 2.1.x. See
# https://docs.ansible.com/ansible/latest/user_guide/become.html#becoming-an-unprivileged-user
# https://docs.ansible.com/ansible/latest/user_guide/become.html#risks-of-becoming-an-unprivileged-user
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'latest' will eventually be wrong, it should keep either within it's version (2.11) or be relative (why it should use doclink)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as we leave it hard-coded to /ansible/latest, I think this is the best we can do. There are no docs at the URL /ansible/2.11/. At any rate, I didn't change that part in this PR - if we want to fix it to use relative links we can do that in another PR. Meanwhile at least this will take users to a relevant section of the docs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the advice on handling the risks of becoming an unprivileged user have not changed, nor are they likely to.

@acozine acozine merged commit 4da2e2d into ansible:stable-2.11 May 4, 2021
@sivel sivel removed the needs_triage Needs a first human triage before being processed. label May 25, 2021
@ansible ansible locked and limited conversation to collaborators Jun 1, 2021
@acozine acozine deleted the backport/2.11/74448 branch June 3, 2021 21:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.11 backport This PR does not target the devel branch. core_review In order to be merged, this PR must follow the core review workflow. docs This issue/PR relates to or includes documentation. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants