chore(docs): update legacy docs site links with new one

pabloopez · pabloopez · commit b41735ec6ea5 · 2025-06-24T14:19:09.000+02:00
diff --git a/docs/resources/entitlement.md b/docs/resources/entitlement.md
@@ -2,7 +2,7 @@
 
 The entitlement resource allows the creation and management of Entitlement tokens for a given Cloudsmith repository. Entitlement tokens grant read-only access to a repository and can be configured with a number of custom restrictions if necessary.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/entitlements) for full entitlement documentation.
+See [help.cloudsmith.io](https://docs.cloudsmith.com/software-distribution/entitlement-tokens) for full entitlement documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/license_policy.md b/docs/resources/license_policy.md
@@ -2,7 +2,7 @@
 
 The license policy resource allows for creation and management of license policies within a Cloudsmith organization.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/license-policies) for the full license policies documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/policy-management/license-policy) for the full license policies documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/repository.md b/docs/resources/repository.md
@@ -2,7 +2,7 @@
 
 The repository resource allows creation and management of package repositories within a Cloudsmith namespace. Repositories store packages and are the main entities with which Cloudsmith users interact.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/manage-a-repository) for full repository documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/repositories) for full repository documentation.
 
 # Example Usage
 
diff --git a/docs/resources/repository_geo_ip_rules.md b/docs/resources/repository_geo_ip_rules.md
@@ -2,7 +2,7 @@
 
 The repository geo/ip rules resource allows the management of geo/ip rules for a given Cloudsmith repository. Using this resource it is possible to allow and/or deny access to a repository using CIDR notation, two-character ISO 3166-1 country codes or a combination thereof.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/geoip-restriction) for full geo/ip rules documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/policy-management/geoip-rules) for full geo/ip rules documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/repository_privileges.md b/docs/resources/repository_privileges.md
@@ -4,7 +4,7 @@ The repository privileges resource allows the management of privileges for a giv
 
 Note that while users can be added to repositories in this manner, since Terraform does not (and cannot currently) manage those user accounts, you may encounter issues if the users change or are deleted outside of Terraform.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/permissions#repository-permissions) for full permissions documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/repositories/repository-settings#repository-privileges) for full permissions documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/repository_retention.md b/docs/resources/repository_retention.md
@@ -6,7 +6,7 @@ Note that while retention rules can be managed in this manner, changes made outs
 
 **Note: Retention rule settings are only applied once retention is enabled for the repository.**
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/retention-lifecycle#:~:text=Retention%20rules%20only%20activate%20when,1000%20day%20package%20be%20deleted.) for full retention rules documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/artifact-management/retention-rules) for full retention rules documentation.
 
 ## Example Usage
 
@@ -42,8 +42,8 @@ resource "cloudsmith_repository_retention_rule" "retention_rule" {
 The following arguments are supported:
 
 * `namespace` - (Required) The namespace of the repository.
-* `repository` - (Required) If true, the retention lifecycle rules will be activated for the repository and settings will be updated.
-* `retention_enabled` - (Required) If true, the retention lifecycle rules will be activated for the repository and settings will be updated.
+* `repository` - (Required) If true, the retention rules will be activated for the repository and settings will be updated.
+* `retention_enabled` - (Required) If true, the retention rules will be activated for the repository and settings will be updated.
 * `retention_count_limit` - (Optional) The maximum number of packages to retain. Must be between 0 and 10000.
 * `retention_days_limit` - (Optional) The number of days of packages to retain. Must be between `0` and `180`.
 * `retention_group_by_name` - (Optional) If true, retention will apply to groups of packages by name rather than all packages.
diff --git a/docs/resources/repository_upstream.md b/docs/resources/repository_upstream.md
@@ -2,7 +2,7 @@
 
 The repository upstream resource allows the management of upstreams for a Cloudsmith repository. Using this resource, it is possible to proxy and/or cache packages hosted in one or more third-party package registries through a single Cloudsmith repository.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/proxying) for full upstream proxying documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/tbc/upstream-proxying-and-caching#supported-formats) for full upstream proxying documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/service.md b/docs/resources/service.md
@@ -2,7 +2,7 @@
 
 The service resource allows the creation and management of services for a given Cloudsmith organization. Services allow users to create API keys that can be used for machine-to-machine or other programmatic access without requiring a real user account.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/service-accounts) for full service documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/accounts-and-teams/service-accounts) for full service documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/team.md b/docs/resources/team.md
@@ -2,7 +2,7 @@
 
 The teams resource allows creation and management of teams within a Cloudsmith organization.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/teams) for full team documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/accounts-and-teams/teams) for full team documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/vulnerability_policy.md b/docs/resources/vulnerability_policy.md
@@ -2,7 +2,7 @@
 
 The vulnerability policy resource allows for creation and management of vulnerability policies within a Cloudsmith organization.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/vulnerability-policy) for the full vulnerability policies documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/policy-management/vulnerability-policy) for the full vulnerability policies documentation.
 
 ## Example Usage
 
diff --git a/docs/resources/webhook.md b/docs/resources/webhook.md
@@ -2,7 +2,7 @@
 
 The webhook resource allows the creation and management of webhooks for a given Cloudsmith repository. Webhooks allow integration with external systems by emitting events via HTTP POST request.
 
-See [help.cloudsmith.io](https://help.cloudsmith.io/docs/webhooks) for full webhook documentation.
+See [docs.cloudsmith.com](https://docs.cloudsmith.com/logs-and-observability/webhooks) for full webhook documentation.
 
 ## Example Usage
 
diff --git a/examples/iterative-example/README.md b/examples/iterative-example/README.md
@@ -6,7 +6,7 @@ shares many attributes with the others, but changes slightly based on their indi
 * Creates a Development, Staging and Production repository
   * Disables User entitlements. The default entitlement token can then be disabled so that authentication can only be done via API keys!
 * Creates an individual CI service account for each repository which gets write access
-  * Configures Github OIDC for authenticating as the service accounts (see our documentation [here](https://help.cloudsmith.io/docs/setup-cloudsmith-to-authenticate-with-oidc-in-github-actions) for how to configure that on the Github side)
+  * Configures Github OIDC for authenticating as the service accounts (see our documentation [here](https://docs.cloudsmith.com/access-control/setup-cloudsmith-to-authenticate-with-oidc-in-github-actions) for how to configure that on the Github side)
 * Creates a Developers team which gets write permission on the Development repository
 * Configures DockerHub and Chainguard upstreams on each repository
 * Configures a Vulnerablity policy that blocks high severity vulnerabilities.
