remove deprecated node-api-check - archived for when there is time to…

… maintain the tool

documentation/docs/next.config.js

@@ -497,13 +497,6 @@ const config = {
         permanent: true,
         basePath: false,
       },
-      {
-        source: "/operators/testing/node-api-check.html",
-        destination:
-          "/docs/operators/nodes/performance-and-testing/node-api-check",
-        permanent: true,
-        basePath: false,
-      },
       {
         source: "/operators/testing/prometheus-grafana.html",
         destination:
@@ -663,13 +656,6 @@ const config = {
         permanent: true,
         basePath: false,
       },
-      {
-        source: "/docs/operators/testing/node-api-check",
-        destination:
-          "/docs/operators/nodes/performance-and-testing/node-api-check",
-        permanent: true,
-        basePath: false,
-      },
       {
         source: "/docs/operators/nodes/proxy-configuration",
         destination:

documentation/docs/pages/operators/changelog.mdx

@@ -659,7 +659,7 @@ systemctl daemon-reload && service nym-node restart
 
 - Since `v2024.13-magura`, operators do not update their node version in the wallet. [Manual upgrading steps](nodes/maintenance/manual-upgrade.mdx) has been updated accordingly.
 
-- CLI tool [`node_api_check.py`](nodes/performance-and-testing/node-api-check.mdx), helping operators to collect all API values about their nodes locally, is not up to date with the API changes introduced with `v2024.13-magura` release version. Please treat it as unstable before we fix it.
+- CLI tool `node_api_check.py`, helping operators to collect all API values about their nodes locally, is not up to date with the API changes introduced with `v2024.13-magura` release version. Please treat it as unstable before we fix it.
 
 #### Error Log
 
@@ -967,7 +967,7 @@ Confirm that the deployment workflows work through manual testing
 ### Operators Updates & Tooling
 
 <Callout type="warning" emoji="⚠️">
-**Every operator has to make sure that their nodes [self-described endpoint works](nodes/performance-and-testing/node-api-check#basic-api-usage), otherwise the node will be un-routable and thus won't get any rewards!**
+**Every operator has to make sure that their nodes self-described endpoint works, otherwise the node will be un-routable and thus won't get any rewards!**
 </Callout>
 
 - **New technical documentation:** All Nym documentation starts from a new entry page [nymtech.net/docs](https://nymtech.net/docs/operators/introduction). To run locally or propose collaboration, start in our [repository](https://github.com/nymtech/nym/tree/develop/documentation)
@@ -1165,7 +1165,7 @@ Some endpoints got purposely deprecated without any equivalent reimplemented sin
 ##### Mixnet Contract
 
 <Callout type="warning" emoji="">
-**Every operator has to make sure that their nodes [self-described endpoint works](nodes/performance-and-testing/node-api-check#basic-api-usage), otherwise the node will be un-routable and thus won't get any rewards!**
+**Every operator has to make sure that their nodes self-described endpoint works, otherwise the node will be un-routable and thus won't get any rewards!**
 </Callout>
 
 ###### High Level Changes
@@ -1979,7 +1979,7 @@ done
     - Vesting contract functionalities have been purged, users can only remove tokens from vesting
     - Migrating from `mixnode` or `gateway` smart contracts to a new unifying `nym-node` smart contract will be available soon using Nym desktop wallet, just like you are used to for bonding and node settings. After this migration all `nym-nodes` will be able to receive delegation and rewards. We will share a step by step guide once this migration will be deployed. No action needed now.
 
-- [Nym API Check CLI](testing/node-api-check.md) is upgraded according to the latest API endpoints, output is cleaner and more concise.
+- Nym API Check CLI is upgraded according to the latest API endpoints, output is cleaner and more concise.
 
 
 #### Operators Tasks
@@ -2868,7 +2868,7 @@ warning: /home/alice/src/nym/nym/common/dkg/Cargo.toml: `default-features` is ig
     - Flow [chart](release-cycle.md#release-flow)
 - [Sandbox testnet](sandbox.md) guide: teaching Nym node operators how to run their nodes in Nym Sandbox testnet environment.
 - [Terms & Conditions flag](nodes/setup.md#terms--conditions)
-- [Node API Check CLI](testing/node-api-check.md)
+- Node API Check CLI
 - [Pruning VPS `syslog` scripts](troubleshooting/vps-isp.md#pruning-logs)
 - [Black-xit: Exiting the blacklist](troubleshooting/nodes.md#my-gateway-is-blacklisted)
 

documentation/docs/pages/operators/nodes/performance-and-testing/_meta.json

@@ -1,5 +1,4 @@
 {
   "gateway-probe": "Gateway Probe",
-  "node-api-check": "Node API Check",
   "prometheus-grafana": "Prometheus & Grafana"
 }

documentation/docs/pages/operators/troubleshooting/nodes.mdx

@@ -113,8 +113,6 @@ There are a few community explorers as well.
 
 Enter your **identity key** to find your node. Check the contents of the `Mixnode stats` and `Routing score` sections.
 
-You can run [Node API Check CLI](../testing/node-api-check.mdx) to query all API endpoints of your node at once.
-
 [Here](https://github.com/cosmos/chain-registry/blob/master/nyx/chain.json#L158-L187) is a dictionary with Nyx chain registry entry regarding all explorers.
 
 If you want more information, or if your node isn't showing up on the explorer of your choice and you want to double-check, here are some examples on how to check if the node is configured properly.
@@ -345,7 +343,7 @@ In case your Gateway appeared on the [blacklist](https://validator.nymtech.net/a
 
 **What to do**
 
-Begin with a sanity check by opening [harbourmaster.nymtech.net](https://harbourmaster.nymtech.net) and check your node there. To query all API endpoints of your node at once, you can run [Node API Check CLI](../testing/node-api-check.mdx). To see IPv4 and IPv6 routing in real time (harbourmaster can have a cache up to 90 min), run [Gateway Probe CLI](../testing/gateway-probe.mdx).
+Begin with a sanity check by opening [harbourmaster.nymtech.net](https://harbourmaster.nymtech.net) and check your node there. To see IPv4 and IPv6 routing in real time (harbourmaster can have a cache up to 90 min), run [Gateway Probe CLI](../testing/gateway-probe.mdx).
 
 Then follow these steps: