Open ntap-bmegan opened 1 month ago
At this point, I can't imagine that anyone is accessing any cloud-tiering URLs. We could request data to confirm that, but I'm not sure that's necessary.
Do we need some sort of higher-level policy that defines how long we retain redirects for?
Do we need some sort of higher-level policy that defines how long we retain redirects for?
Probably. 🥲
I usually recommend redirects for 1-2 years. That said, we've had 'errors' where our clouddocs.netapp.com redirects stopped working, and people complained -- 5+ years after implementation.
Any permanent redirect in our web-proxy or Switchboard can be maintained without a repository. Any temporary redirects using the frontmatter redirect
field still requires that original page to exist, as the redirect is performed from the user's browser instead of our server. List: https://github.com/search?q=org%3ANetAppDocs%20redirect&type=code. Teams such as ONTAP are using this to redirect a select set of pages (renamed, deleted, etc) without having to specify redirects for their entire site/folder.
@netapp-bcammett - Do you want individual page redirects or can we just redirect everything to a single location? I'm inclined to think that the bar after 4 years is pretty low, specifically not to 404.
I think we can safely remove the redirects and archive this repo. It's been long enough.
Summary
@netapp-bcammett & @akseldavis
The URL https://docs.netapp.com/us-en/cloud-tiering/ redirects to https://docs.netapp.com/us-en/bluexp-tiering/concept-cloud-tiering.html. It looks like the last time that the repo was touched was four years ago in https://github.com/NetAppDocs/cloud-tiering/commit/de6fe15b641fd8f0032cb5ce1cf5208189eae0c6.
Do we still need page-level redirects after four years? If we still need any redirects, can we handle them without maintaining a repository?
Note that there is no internal repo, just the public English.
Public issues must not contain sensitive information