add docUrlServerless field to endpoints

[miguelgrinberg]

Fixes #5188 (partially)

This change adds a column to table.csv for documentation URLs that apply to serverless. The new column is inserted in the 3rd position, right after doc-url. The value can be a URL, empty when there is no serverless equivalent, or the string [use-doc-url] to use the same URL for both stack and serverless.

The new documentation URLs are included in schema.json for all endpoints with the name docUrlServerless.

This change adds the support for generating the URLs. The table.csv entries are all set to [use-doc-url] for now. The docs team needs to fill URLs that are different as needed.

[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.

[Anaethelion]

LGTM

[miguelgrinberg]

@lcawl This PR is waiting for you now. The 3rd column in table.csv is now the serverless doc url. If you leave it set to [use-doc-url] then the same URL is used for both. This is what I put in all the entries for now. You can replace this with a real URL, or with an empty string when there is no URL. Thanks!

[pquentin]

Even though this is only for serverless, I added the backport 9.1 and backport 9.2 labels in the interest of reducing merge conflicts down the road, as the table.csv file is a big source of merge conflicts. Case in point, we have a conflict on this file right now.

[lcawl]

I rebased this PR to catch the three PRs that had added rows in the table.csv file. I then used an AI script to update the file as follows: 271 rows were updated with valid serverless URLs, and 264 rows that contained Elasticsearch API URLs were skipped because their serverless URLs returned 404. I have left the latter as [use-doc-url] for now.

[Edit] On second thought, I set those 264 rows to an empty value instead, to more accurately indicate that they don't exist.

[lcawl]

This does seem to address my original issue, thanks! It also addresses the situation where we have serverless-only APIs like #5874

It might be cool to use that new serverless-specific column for all URL resolution in the serverless-specific OpenAPI output, but that can be discussed as a follow-up.

[miguelgrinberg]

@lcawl Do you want to give this PR a last look before we merge? I had to do another merge of the main branch, and that came with one new row in table.csv, the one for cef-processor.

[github-actions]

The backport to 9.1 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.1 9.1
# Navigate to the new working tree
cd .worktrees/backport-9.1
# Create a new branch
git switch --create backport-5851-to-9.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79acfd91b6a1341650995f789a3378f54122662b
# Push it to GitHub
git push --set-upstream origin backport-5851-to-9.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.1

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

[github-actions]

The backport to 9.2 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.2 9.2
# Navigate to the new working tree
cd .worktrees/backport-9.2
# Create a new branch
git switch --create backport-5851-to-9.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79acfd91b6a1341650995f789a3378f54122662b
# Push it to GitHub
git push --set-upstream origin backport-5851-to-9.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.2

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

[github-actions]

The backport to 9.3 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.3 9.3
# Navigate to the new working tree
cd .worktrees/backport-9.3
# Create a new branch
git switch --create backport-5851-to-9.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79acfd91b6a1341650995f789a3378f54122662b
# Push it to GitHub
git push --set-upstream origin backport-5851-to-9.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.3

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