chore: archive legacy enterprise versions 22.4 and 23.1-23.4

changelog/seqera-enterprise/v22.3.md

@@ -126,7 +126,7 @@ This feature is currently only available on Tower Cloud (tower.nf). For more inf
 
 - Use of the resource labels feature with AWS Batch requires an update of the IAM policy used by the account running Tower. The required changes can be found [here](https://github.com/seqeralabs/nf-tower-aws/commit/65b4659d93c0639ea95cc96369865b328a17bb15).
 
-- In previous versions, if Tower was configured to [authenticate to AWS via instance role](https://install.tower.nf/22.3/advanced-topics/use-iam-role/), Batch Forge would assign this same IAM Role as the [Head Job role and Compute Job role](https://docs.seqera.io/platform-enterprise/23.3/compute-envs/aws-batch/#advanced-options) of the AWS Batch compute environment it created. As of version 22.3.1, you must explicitly assign these job roles during the AWs Batch compute environment creation process.
+- In previous versions, if Tower was configured to [authenticate to AWS via instance role](https://install.tower.nf/22.3/advanced-topics/use-iam-role/), Batch Forge would assign this same IAM Role as the [Head Job role and Compute Job role](https://docs-archive.seqera.io/platform-enterprise/23.3/compute-envs/aws-batch/#advanced-options) of the AWS Batch compute environment it created. As of version 22.3.1, you must explicitly assign these job roles during the AWs Batch compute environment creation process.
 
 ### Warnings
 

changelog/seqera-enterprise/v22.4.md

@@ -35,7 +35,7 @@ The **All runs** view is accessible via the user menu.
 
 All Tower instances with internet access can now connect to the Seqera Labs Wave container service to leverage its container augmentation and Fusion v2 file system capabilities. See the [Wave containers documentation](https://docs.seqera.io/nextflow/wave) for more information about Wave containers.
 
-The Wave integration also allows for the secure transfer of credentials required to access private registries between services. See the [Tower documentation](https://docs.seqera.io/platform-enterprise/23.3) to learn how to use the feature in your enterprise installation.
+The Wave integration also allows for the secure transfer of credentials required to access private registries between services. See the [Tower documentation](https://docs-archive.seqera.io/platform-enterprise/23.3) to learn how to use the feature in your enterprise installation.
 
 ### Fusion file system support
 

changelog/seqera-enterprise/v23.1.md

@@ -70,7 +70,7 @@ Several new Tower features over the last few releases require updated AWS IAM pe
 
 ### Wave requires container registry credentials
 
-The Wave containers service uses container registry [credentials](https://docs.seqera.io/platform-enterprise/23.1/credentials/overview) in your Seqera instance to authenticate to your (public or private) container registries. This is separate from your existing cloud provider credentials stored in your Seqera instance.
+The Wave containers service uses container registry [credentials](https://docs-archive.seqera.io/platform-enterprise/23.1/credentials/overview) in your Seqera instance to authenticate to your (public or private) container registries. This is separate from your existing cloud provider credentials stored in your Seqera instance.
 
 This means that, for example, AWS ECR (Elastic Container Registry) authentication requires an [ECR container registry credential](https://docs.seqera.io/platform-cloud/23.1/credentials/aws_registry_credentials) if you are running a compute environment with Wave enabled, even if your existing AWS credential in Tower has IAM access to your ECR.
 
@@ -108,7 +108,7 @@ If you must host your nf-launcher container image on a private image registry, c
     `TOWER_LAUNCH_CONTAINER=<FULL_PATH_TO_YOUR_PRIVATE_IMAGE>`
 
 !!! warning ""
-    If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/23.1/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
+    If you're using AWS Batch, you will need to [configure a custom job definition](https://docs-archive.seqera.io/platform-enterprise/23.1/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
 
 ## Sharing feedback
 

changelog/seqera-enterprise/v23.2.md

@@ -82,11 +82,11 @@ Several new Tower features over the last few releases require updated AWS IAM pe
 
 ### Wave requires container registry credentials
 
-The Wave containers service uses container registry [credentials](https://docs.seqera.io/platform-enterprise/23.2/credentials/overview) in Tower to authenticate to your (public or private) container registries. This is separate from your existing cloud provider credentials stored in Tower.
+The Wave containers service uses container registry [credentials](https://docs-archive.seqera.io/platform-enterprise/23.2/credentials/overview) in Tower to authenticate to your (public or private) container registries. This is separate from your existing cloud provider credentials stored in Tower.
 
-This means that, for example, AWS ECR (Elastic Container Registry) authentication requires an [ECR container registry credential](https://docs.seqera.io/platform-enterprise/23.2/credentials/aws_registry_credentials) if you are running a compute environment with Wave enabled, even if your existing AWS credential in Tower has IAM access to your ECR.
+This means that, for example, AWS ECR (Elastic Container Registry) authentication requires an [ECR container registry credential](https://docs-archive.seqera.io/platform-enterprise/23.2/credentials/aws_registry_credentials) if you are running a compute environment with Wave enabled, even if your existing AWS credential in Tower has IAM access to your ECR.
 
-See the relevant [container registry credentials](https://docs.seqera.io/platform-enterprise/23.2/credentials/overview) page for provider-specific instructions.
+See the relevant [container registry credentials](https://docs-archive.seqera.io/platform-enterprise/23.2/credentials/overview) page for provider-specific instructions.
 
 ## Upgrade steps
 

changelog/seqera-enterprise/v23.3.md

@@ -76,7 +76,7 @@ When a run completes successfully, Seqera automatically creates an _optimized pr
 
 **Login redirection logic update**
 
-Login redirection logic has changed in version 23.3. Seqera now prepends the [`TOWER_SERVER_URL`](https://docs.seqera.io/platform-enterprise/23.3/enterprise/configuration/overview#basic-configuration) (or `tower.serverUrl` in `tower.yml` configuration) to the authentication redirect URL during the login flow. This is useful when your server URL contains a contextual path.
+Login redirection logic has changed in version 23.3. Seqera now prepends the [`TOWER_SERVER_URL`](https://docs-archive.seqera.io/platform-enterprise/23.3/enterprise/configuration/overview#basic-configuration) (or `tower.serverUrl` in `tower.yml` configuration) to the authentication redirect URL during the login flow. This is useful when your server URL contains a contextual path.
 
 If you specify a DNS name as your `TOWER_SERVER_URL`, but access your Seqera instance using a different address (such as using an IP address that resolves to the server URL asynchronously), user login will not resolve.
 

changelog/seqera-enterprise/v23.4.md

@@ -66,7 +66,7 @@ When a cloud storage location is provided as the pipeline work directory in a cl
 
 **Login redirection logic update**
 
-Login redirection logic has changed in version 23.4. Seqera now prepends the [`TOWER_SERVER_URL`](https://docs.seqera.io/platform-enterprise/23.4/enterprise/configuration/overview) (or `tower.serverUrl` in `tower.yml` configuration) to the authentication redirect URL during the login flow. This is useful when your server URL contains a contextual path.
+Login redirection logic has changed in version 23.4. Seqera now prepends the [`TOWER_SERVER_URL`](https://docs-archive.seqera.io/platform-enterprise/23.4/enterprise/configuration/overview) (or `tower.serverUrl` in `tower.yml` configuration) to the authentication redirect URL during the login flow. This is useful when your server URL contains a contextual path.
 
 If you specify a DNS name as your `TOWER_SERVER_URL`, but access your Seqera instance using a different address (such as using an IP address that resolves to the server URL asynchronously), user login will not resolve.
 
@@ -130,7 +130,7 @@ If you must host your nf-launcher container image on a private image registry, c
     `TOWER_LAUNCH_CONTAINER=<FULL_PATH_TO_YOUR_PRIVATE_IMAGE>`
 
 :::caution
-If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/23.4/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
+If you're using AWS Batch, you will need to [configure a custom job definition](https://docs-archive.seqera.io/platform-enterprise/23.4/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
 :::
 
 [gcp-vm-instance-template]: https://cloud.google.com/compute/docs/instance-templates