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

Retire AWS guide #3718

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AkshayGadhaveRH
Copy link
Contributor

  • Move Deployment scenarios to Planning Guide.
  • Move Prerequisites to Installing Guide.

JIRA: https://issues.redhat.com/browse/SAT-30032

What changes are you introducing?

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.14/Katello 4.16
  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • Foreman 3.8/Katello 4.10
  • Foreman 3.7/Katello 4.9 (Satellite 6.14)
  • We do not accept PRs for Foreman older than 3.7.

- Move Deployment scenarios to Planning Guide.
- Move Prerequisites to Installing Guide.

JIRA: https://issues.redhat.com/browse/SAT-30032
@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Mar 10, 2025
Copy link

@maximiliankolb
Copy link
Contributor

Hey @AkshayGadhaveRH I am currently working on this too. I'd like to have #3485 and #3634 merged first. Then, I also planned to move the AWS-specific content into "Planning for Foreman". If you want to take over this third step, I'd be very happy. But please give me some more time to get reviews/ACKs on my PRs.

@maximiliankolb
Copy link
Contributor

Hi Akshay, both other PRs have been merged. Please rebase your PR to HEAD of "master". If you have finished your work on this PR, please mark if "ready for review".

@AkshayGadhaveRH
Copy link
Contributor Author

ack @maximiliankolb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing Not yet reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants