bug: --apihost flag limitations

[WilliamBergamin]

Description

The --apihost flag is mainly used by the maintainers of this project to test various use cases. Using it as follows --apihost=api.shhhh.slack.com mostly works as expected. But when combine with the deploy command having the api domain prefix breaks the logic that sets the SLACK_API_URL environment variable

Version

Using lack v3.3.0

OS Info

ProductName:            macOS
ProductVersion:         15.5
BuildVersion:           24F74
Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:49 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6000

Steps to reproduce:

Share the commands to run, source code, and project settings:

1. Create an app
2. Use commands with the --apihost flag set to a value prefixed with api.
   a. everything should work as expected
3. Use slack deploy --apihost=api.your.test.endpoint -vv
4. No error is raised and no trace of a request to set the SLACK_API_URL environment variable can be found
5. If the flag value is set without the api prefix the SLACK_API_URL environment variable is set and things work as expected

Expected result:

If the apihost value is rejected the CLI expects then we should inform the user

Actual result:

Nothing indicates that the apihost value is rejected by the CLI

Requirements

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

[mwbrooks]

Thanks @WilliamBergamin!

Perhaps we should call the api.test method when the CLI is starting up. If it fails, we know that the API host has been configured incorrectly. I believe this is something that the Bolt Frameworks do as well. However, we'll want to exempt some commands from requiring a network, such as version. 🤔

[zimeg]

🔍 Surfacing more findings from the kind @WilliamBergamin following!

Saved credentials with a custom API host might not be overwritten during execution when using an explicit flag:

$ lack run --apihost="https://dev1815.slack.com/"
...
🚫 HTTP request failed (http_request_failed)
   unexpected status code 503 returned from url https://dev2126.slack.com/api/tooling.tokens.rotate

Note: Both development hosts are referencing the same team.

We might prefer to use this flag value for all methods while also skipping token rotation if that's provided to avoid these errors?