Forge verify-contract does not honor [etherscan] configs in foundry.toml for certain chains when using --chain

[ezynda3]

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

forge 0.2.0 (9d64f1f 2022-10-26T00:08:20.899561012Z)

What command(s) is the bug in?

forge verify-contract

Operating System

Linux

Describe the bug

Given I have [etherscan] config settings in foundry.toml like so

[etherscan]
mainnet = { key = "${MAINNET_ETHERSCAN_API_KEY}" }
polygon = { key = "${POLYGON_ETHERSCAN_API_KEY}", url = "https://api.polygonscan.com/api" }
bsc = { key = "${BSC_ETHERSCAN_API_KEY}", url = "https://api.bscscan.com/api" }
gnosis = { key = "${GNOSIS_ETHERSCAN_API_KEY}", url = "https://blockscout.com/poa/xdai/api" }

When running forge verify-contract --chain gnosis ... I get the following error

error: Invalid value "gnosis" for '--chain <CHAIN>': Expected known chain or integer, found: gnosis

When using --chain mainnet or --chain polygon the command runs with no issues.

I would expect that forge verify-contract would honor the configuration in my foundry.toml file