update link workflow (#335)

* update link workflow

* fix links

* more fixes

* ignore hashicorp urls

Author: alexandratran

.github/workflows/link-check.json

@@ -11,12 +11,9 @@ jobs:
   linkCheck:
     name: Link Checking
     runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        file-extensions: [".md", ".mdx"]
     steps:
       - uses: actions/checkout@v4
       - name: LinkCheck
         uses: ConsenSys/github-actions/docs-link-check@main
         with:
-          FILE_EXTENSION: ${{ matrix.file-extensions }}
+          CONFIG_FILE: .linkspector.yml

.github/workflows/links.yml

@@ -0,0 +1,26 @@
+dirs:
+  - ./docs
+excludedDirs:
+  - ./build
+  - ./.vercel
+  - ./.docusaurus
+  - ./node_modules
+  - ./version_docs
+useGitIgnore: true
+
+ignorePatterns:
+- pattern: '^http(s)?://localhost'
+- pattern: '^http(s)?://127.0.0.1'
+- pattern: '^http(s)?://gitlab.com/ConsenSys/'
+- pattern: '^http(s)?://consensys.net'
+- pattern: '^http(s)?://.+.zendesk.com'
+- pattern: '^http(s)?://.+.etherscan.io'
+- pattern: '^http(s)?://help.figma.com'
+- pattern: '^http(s)?://metamask.io'
+- pattern: '^http(s)?://.*\.hashicorp\.com'
+- pattern: '^/img/'
+aliveStatusCodes:
+- 200
+- 206
+- 400
+- 403

.linkspector.yml

@@ -41,7 +41,7 @@ web3signer --key-store-path=/Users/me/keyFiles/ eth1
 
 In the command line:
 
-- Use the [`--key-store-path`](../reference/cli/options.md#key-store-path) option to specify the
+- Use the [`--key-store-path`](../reference/cli/options.md#key-config-path-key-store-path) option to specify the
   location of the signing key configuration files.
 - Specify the [subcommand] to indicate which signing mode to use.
   Valid subcommands are `eth2` and `eth1`.

docs/get-started/start-web3signer.md

@@ -70,7 +70,7 @@ web3signer --key-store-path=/Users/me/keyFiles/ \
 The command line:
 
 - Specifies the location of the signing key configuration files using the
-  [`--key-store-path`](../reference/cli/options.md#key-store-path) option.
+  [`--key-store-path`](../reference/cli/options.md#key-config-path-key-store-path) option.
 - Specifies the Web3Signer keystore using the
   [`--tls-keystore-file`](../reference/cli/options.md#tls-keystore-file) option.
 - Specifies the file that contains the password to decrypt the keystore using the
@@ -133,9 +133,9 @@ The command line:
 - Enables TLS using the
   [`--downstream-http-tls-enabled`](../reference/cli/subcommands.md#downstream-http-tls-enabled) option.
 - Specifies the keystore to present during authentication using the
-  [`--downstream-http-tls-keystore-file`](../reference/cli/subcommands.md#downstream-http-tls-keystore-file) option.
+  `--downstream-http-tls-keystore-file` option.
 - Specifies the file that contains the password to decrypt the keystore using the
-  [`--downstream-http-tls-keystore-password-file`](../reference/cli/subcommands.md#downstream-http-tls-keystore-password-file) option.
+  `--downstream-http-tls-keystore-password-file` option.
 - [Specifies the servers](#create-the-known-servers-file) to connect to using the
   [`--downstream-http-tls-known-servers-file`](../reference/cli/subcommands.md#downstream-http-tls-known-servers-file) option.
 

docs/how-to/configure-tls.md

@@ -38,7 +38,7 @@ single file by adding a triple-dash separator (`---`) between configurations.
 The configuration file must be YAML-formatted, and can use any naming format, but must have the `.yaml` extension.
 
 Place one or more key configuration files in a single directory which you specify when starting Web3Signer.
-Use the [`--key-store-path`](../reference/cli/options.md#key-store-path) option to specify the
+Use the [`--key-store-path`](../reference/cli/options.md#key-config-path-key-store-path) option to specify the
 location of the key configuration files.
 
 ```bash

docs/how-to/load-keys.md

@@ -9,7 +9,7 @@ sidebar_position: 1
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-Web3Signer supports storing the signing key in [HashiCorp Vault](https://www.hashicorp.com/products/vault/).
+Web3Signer supports storing the signing key in [HashiCorp Vault](https://www.hashicorp.com/en/products/vault).
 
 ## Store a private key in HashiCorp Vault
 

docs/how-to/store-keys/vaults/hashicorp.md

@@ -96,7 +96,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sign","params":["0x78e6e2365
 ## `eth_signTransaction`
 
 Signs a transaction that you can submit to Besu at a later time using
-[`eth_sendRawTransaction`](https://besu.hyperledger.org/stable/public-networks/reference/api#eth_sendrawtransaction).
+[`eth_sendRawTransaction`](https://besu.hyperledger.org/public-networks/reference/api#eth_sendrawtransaction).
 
 ### Parameters
 
@@ -226,7 +226,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_signTypedData","params":["0x
 Creates and signs a transaction using the signing key.
 
 Web3Signer submits the signed transaction to Besu using
-[`eth_sendRawTransaction`](https://besu.hyperledger.org/stable/public-networks/reference/api#eth_sendrawtransaction).
+[`eth_sendRawTransaction`](https://besu.hyperledger.org/public-networks/reference/api#eth_sendrawtransaction).
 
 ### Parameters
 

docs/reference/api/json-rpc.md

@@ -727,7 +727,7 @@ eth1.chain-id: "2017"
 </Tabs>
 
 ID of the chain to receive the signed transactions. The Besu documentation
-lists [chain IDs for public networks](https://besu.hyperledger.org/development/public-networks/concepts/network-and-chain-id).
+lists [chain IDs for public networks](https://besu.hyperledger.org/public-networks/concepts/network-and-chain-id).
 
 #### `downstream-http-host`
 

docs/reference/cli/subcommands.md

@@ -41,7 +41,7 @@ web3signer --key-store-path=/Users/me/keyFiles/ eth1
 
 In the command line:
 
-- Use the [`--key-store-path`](../reference/cli/options.md#key-store-path) option to specify the
+- Use the [`--key-store-path`](../reference/cli/options.md#key-config-path-key-store-path) option to specify the
   location of the signing key configuration files.
 - Specify the [subcommand] to indicate which signing mode to use.
   Valid subcommands are `eth2` and `eth1`.