Project

Profile

Help

Issue #7065

Ansible playbook examples in Pulpcore docs and Pulp Ansible installer docs differ

Added by mcorr 3 months ago. Updated about 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Sprint 79
Quarter:

Description

Firstly, I was looking at the Ansible installer entry in Pulpcore docs https://docs.pulpproject.org/installation/instructions.html#ansible-installation-recommended with a view to suggesting we add a summary here and a link to the Ansible installer docs, so that the content only needs to be updated once. I think they might be slipping out of date.

Secondly, I noticed that there is a disparity between the example playbooks shown in the docs:

https://docs.pulpproject.org/installation/instructions.html#ansible-installation-recommended

vs

https://pulp-installer.readthedocs.io/en/latest/quickstart/#example-playbook-for-installing-plugins

Which is more up to date?

If you're happy for me to:

  1. Replace the Ansible installer section in the Pulpcore docs with just a description and redirect to the Pulp Ansible Installer docs
  2. Update the existing playbook if necessary

Please let me know.

Associated revisions

Revision e0fe2ede View on GitHub
Added by mcorr about 2 months ago

Make passwd variable consistent with Ansible docs

fixes #7065

History

#1 Updated by dkliban@redhat.com 3 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 76

#2 Updated by fao89 3 months ago

pulpcore master: https://docs.pulpproject.org/en/master/nightly/installation/instructions.html#ansible-installation-recommended the main difference is about getting attention to set the secret and password, and I agree we should update it on pulpcore

#3 Updated by mdepaulo@redhat.com 3 months ago

I think we should use "<< YOUR SECRET HERE >>", as it is our newer convention, and it is more safe. It prevents users from using a simple guessable secret like that in production.

As fao89 showed, the rest of the playbook on the master branch seems to be identical other than this.

#4 Updated by mcorr 3 months ago

Yep. I wasn't looking at master, just the published docs. I will make that small change!

#5 Updated by mcorr 3 months ago

  • Assignee set to mcorr

#6 Updated by pulpbot 3 months ago

  • Status changed from NEW to POST

#7 Updated by rchan 3 months ago

  • Sprint changed from Sprint 76 to Sprint 77

#8 Updated by rchan 2 months ago

  • Sprint changed from Sprint 77 to Sprint 78

#9 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 78 to Sprint 79

#10 Updated by mcorr about 2 months ago

  • Status changed from POST to MODIFIED

#11 Updated by dkliban@redhat.com about 2 months ago

  • Sprint/Milestone set to 3.6.0

#12 Updated by pulpbot about 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF