foreman-documentation Update Google Compute Engine branding

Replacing Google GCE with GCE, since GCE is an abbreviation of Google Compute Engine.

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

Contributor checklists

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

Please cherry-pick my commits into:

[x] Foreman 3.17/Katello 4.19
[x] Foreman 3.16/Katello 4.18 (Satellite 6.18)
[x] Foreman 3.15/Katello 4.17
[x] Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4)
[x] Foreman 3.13/Katello 4.15 (EL9 only)
[x] Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
[x] Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9; orcharhino 7.1 with Leapp)
[x] Foreman 3.10/Katello 4.12
[x] Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
We do not accept PRs for Foreman older than 3.9.

Summary by Sourcery

Standardize Google Compute Engine branding across documentation and related module filenames.

Documentation:

Update references from Google GCE to GCE in cloud provisioning documentation.
Rename GCE-related procedure modules to match the updated branding in their filenames.

Nov 25 '25 07:11 AkshayGadhaveRH

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR standardizes Google Compute Engine branding in the documentation by replacing the phrase “Google GCE” with the abbreviation “GCE” and aligning related module and assembly filenames accordingly.

File-Level Changes

Change	Details	Files
Standardize GCE branding in provisioning assembly and related procedure modules.	Update the provisioning cloud instances assembly content to use the GCE abbreviation consistently instead of the phrase 'Google GCE'. Rename procedure module files for adding a connection, adding details to a compute profile, deleting a VM, and installing the plugin so that their filenames use 'gce' instead of 'google-gce'. Adjust internal references in affected documents to point to the newly renamed GCE-related modules and ensure cross-references remain valid. Keep related reference documentation (such as port and firewall requirements) in sync with the updated GCE terminology where applicable.	`guides/common/assembly_provisioning-cloud-instances-gce.adoc` `guides/common/modules/proc_adding-a-google-gce-connection.adoc` `guides/common/modules/proc_adding-a-gce-connection.adoc` `guides/common/modules/proc_adding-google-gce-details-to-a-compute-profile.adoc` `guides/common/modules/proc_adding-gce-details-to-a-compute-profile.adoc` `guides/common/modules/proc_deleting-a-vm-on-google-gce.adoc` `guides/common/modules/proc_deleting-a-vm-on-gce.adoc` `guides/common/modules/proc_installing-google-gce-plugin.adoc` `guides/common/modules/proc_installing-gce-plugin.adoc` `guides/common/modules/ref_project-server-port-and-firewall-requirements.adoc`

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an issue from a review comment by replying to it. You can also reply to a review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull request title to generate a title at any time. You can also comment @sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in the pull request body to generate a PR summary at any time exactly where you want it. You can also comment @sourcery-ai summary on the pull request to (re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the pull request to resolve all Sourcery comments. Useful if you've already addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull request to dismiss all existing Sourcery reviews. Especially useful if you want to start fresh with a new review - don't forget to comment @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

Nov 25 '25 07:11 sourcery-ai[bot]

The PR preview for 77364ae6db3bb95db8a9848a69d6d981d9a71511 is available at theforeman-foreman-documentation-preview-pr-4496.surge.sh

The following output files are affected by this PR:

show diff

show diff as HTML

Nov 25 '25 08:11 github-actions[bot]

Found a few places where we still mention Google Compute Engine

@stejskalleos Why is that an issue?

Nov 26 '25 09:11 Lennonka

Cherry picked:

8fd8bb652e..0d3a8f2aa0 3.17 -> 3.17
e7cb5b1eb5..6a92c5d813 3.16 -> 3.16

Conflicts on 3.15. Please, file another PR. @AkshayGadhaveRH

Nov 26 '25 09:11 Lennonka