[editorial] Update database redirect rules

[vitorvasc]

Fixes #3138. Also referenced by open-telemetry/opentelemetry.io#8311.

Changes

• Drops the database alias entries that were added in [chore] Rename */database to */db to match area names #3108.
• Adds a new redirect rule to docs/README.md.

You can test the updates and the redirect rules here: https://deploy-preview-8311--opentelemetry.netlify.app.

When navigating to: https://deploy-preview-8311--opentelemetry.netlify.app/docs/specs/semconv/database/, it now correctly redirects to the new path: https://deploy-preview-8311--opentelemetry.netlify.app/docs/specs/semconv/db/.

[chalin]

Nice, thanks @vitorvasc!

Did you try adding the redirects rule to the db/README.md?

[chalin]

LGTM / is functional as is. I'd prefer having the db redirects more tightly scoped if that'll work. (Approving now in case I can't get back to it later.)

[vitorvasc]

@chalin I did try at first, but I didn't really test it integrating with open-telemetry/opentelemetry.io#8311. I was trying to test everything locally, but none of the redirect rules were working correctly (I'll follow-up about that in the #otel-comms-approvers thread we've been discussing it).

My thinking was that if we added the rule to docs/db/README.md, the redirect would end up being /docs/specs/semconv/db/database/ -> /docs/specs/semconv/db/. In any case, I'll try pushing a few more commits to validate that behavior, I'm not totally sure that's how it actually works.

[chalin]

@vitorvasc

@chalin I did try at first, but I didn't really test it integrating with open-telemetry/opentelemetry.io#8311. I was trying to test everything locally, but none of the redirect rules were working correctly (I'll follow-up about that in the #otel-comms-approvers thread we've been discussing it).

👍🏻 Yeah, Netlify CLI doesn't always play nice when run locally.

My thinking was that if we added the rule to docs/db/README.md, the redirect would end up being /docs/specs/semconv/db/database/ -> /docs/specs/semconv/db/. In any case, I'll try pushing a few more commits to validate that behavior, I'm not totally sure that's how it actually works.

The rules have special-case handling to avoid that. Either you'll need to use from: database/* or from: ./database/* I can't recall which :)

[chalin]

@vitorvasc - even if you can't test using Netlify CLI, you can always inspect the redirects file that gets generated.

[vitorvasc]

@vitorvasc - even if you can't test using Netlify CLI, you can always inspect the redirects file that gets generated.

💡 💡 !

Okay, just tested it by checking the generated _redirect file, and looks well. I've pushed another commit to have the rule more scoped. Thanks! 😄

[chalin]

Thanks again @vitorvasc for trying out the alternatives.
LGTM

[trask]

Thanks!