update logic for x-metatags to use the standard term used by webteam …

[georgewallace]

Updating the new x-metatags logic implemented to update the name. The web team and docs are already leveraging product_name for facets. The current implementation converts the key value pair in the x-metatags area to a head element in the HTML. By changing to product_name this will work as expected with currently workflows with docs and the web team for site search.

[georgewallace]

@l-trotta, @szabosteve , and @lcawl making a minor update to what we just created for the product facets. This will align with what we currently have for docs and the webteam for search. This is related to #4511

[github-actions]

Following you can find the validation changes against the target branch for the APIs.

No changes detected.

You can validate these APIs yourself by using the make validate target.

[l-trotta]

isn't this outdated? #4511 had an update, #4860 where the output format is changed

[georgewallace]

the output format did change. What I am looking for us to change is the table to use actual product names vs the ids as bump has no way to change the logic. And since we went with x-metatags there is no need to have the value in the key value pair be x-product-feature. We can just call it product_name. That is what is going to be passed to the final output on the webpage. cc: @szabosteve Please correct me if I am wrong here.

[georgewallace]

I did double check and the update I made is able to be processed by bump and shows as we expect it to show.

[l-trotta]

if @szabosteve approves then it's fine by me!

[szabosteve]

Thanks for the multiple pings, I just got back and missed some.
As far as I see, this PR changes the product names and changes x-product-feature to product-name. The format Laura provided for bump is still the same (Map).

[github-actions]

The backport to 8.19 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.19 8.19
# Navigate to the new working tree
cd .worktrees/backport-8.19
# Create a new branch
git switch --create backport-4972-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 51504a22d49d51140d6ba568adca866a4cc44388
# Push it to GitHub
git push --set-upstream origin backport-4972-to-8.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.19

Then, create a pull request where the base branch is 8.19 and the compare/head branch is backport-4972-to-8.19.

[github-actions]

The backport to 9.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.0 9.0
# Navigate to the new working tree
cd .worktrees/backport-9.0
# Create a new branch
git switch --create backport-4972-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 51504a22d49d51140d6ba568adca866a4cc44388
# Push it to GitHub
git push --set-upstream origin backport-4972-to-9.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.0

Then, create a pull request where the base branch is 9.0 and the compare/head branch is backport-4972-to-9.0.

[georgewallace]

💚 All backports created successfully

Status	Branch	Result
✅	8.19

Questions ?

Please refer to the Backport tool documentation

[georgewallace]

💚 All backports created successfully

Status	Branch	Result
✅	9.0

Questions ?

Please refer to the Backport tool documentation

[georgewallace]

💚 All backports created successfully

Status	Branch	Result
✅	9.1

Questions ?

Please refer to the Backport tool documentation