Restore community ee content

[oraNod]

This PR restores the docs about community execution environments from the ecosystem docsite. Please see the forum post for more info about this change: https://forum.ansible.com/t/moving-the-community-ee-content-to-package-docs/8239

[oraNod]

This builds for the package docs only, not core docs. I've kicked off a build that will deploy to the test site -> https://github.com/ansible/ansible-documentation/actions/runs/10791538997

@Andersson007 FYI ^

[Andersson007]

@oraNod does the PR just move the content from the old location unchanged? If yes, shipit

[oraNod]

@oraNod does the PR just move the content from the old location unchanged? If yes, shipit

@Andersson007 There is one minor change. I took out the cat ... EOF wrapper for the yaml examples and put them in as native file type. I think it's better so we can lint the yaml files. For instance I found a spacing error and Ansible lint caught the truthy rule violation s/become: yes/become:true.

[Andersson007]

LGTM

[oraNod]

Thanks @Andersson007 Here are the package docs on the stage / test site now: https://ansible-community.github.io/package-doc-builds/getting_started_ee/index.html

[samccann]

LGTM. I'd also remove the 2.15 packport. That equates to Ansible 8 which is EOL.

[oraNod]

LGTM. I'd also remove the 2.15 packport. That equates to Ansible 8 which is EOL.

Thanks @samccann that makes sense to me but I'll defer to @Andersson007 there. Cheers.

[Andersson007]

LGTM, about 2.15: according to the doc it'll be EOL in November . Let's leave it then Ah, i see now you're talking about the package, not sure then. I think i would still backport to supported core branches as if we don't, it could lead to more merge conflicts as sometimes core-specific pages correlates with more general pages

[patchback]

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

❌ Failed to cleanly apply 2043e2e on top of patchback/backports/stable-2.15/2043e2efa0de69f39edee2829934ca141fd1f254/pr-1852

Backporting merged PR #1852 into devel

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/ansible-documentation.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-2.15/2043e2efa0de69f39edee2829934ca141fd1f254/pr-1852 upstream/stable-2.15

4. Now, cherry-pick PR Restore community ee content #1852 contents into that branch:

   $ git cherry-pick -x 2043e2efa0de69f39edee2829934ca141fd1f254

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

   $ git cherry-pick -m1 -x 2043e2efa0de69f39edee2829934ca141fd1f254

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Restore community ee content #1852 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.15/2043e2efa0de69f39edee2829934ca141fd1f254/pr-1852

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-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/2043e2efa0de69f39edee2829934ca141fd1f254/pr-1852

Backported as #1858

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

[patchback]

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/2043e2efa0de69f39edee2829934ca141fd1f254/pr-1852

Backported as #1859

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

[Andersson007]

@oraNod thanks for moving the docs back! @samccann thanks for reviewing!

[oraNod]

The backport to stable-2.15 failed because I don't think the content ever existed on that branch. So let's leave it. It's backported to 2.17 and 2.16 now. We should be good. Thanks again.