bug: --apihost flag limitations
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by reproducing slack deploy --apihost=api.your.test.endpoint -vv and trace the deploy command's --apihost handling and SLACK_API_URL setup. Done means the CLI either handles the api. prefix correctly or clearly informs the user that the value is rejected; verify the behavior with and without that prefix.
Written by the indexing model from the issue text.
Description
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:
- Create an app
- Use commands with the
--apihostflag set to a value prefixed withapi.
a. everything should work as expected - Use
slack deploy --apihost=api.your.test.endpoint -vv - No error is raised and no trace of a request to set the
SLACK_API_URLenvironment variable can be found - If the flag value is set without the
apiprefix theSLACK_API_URLenvironment 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.
- Dominant language
- Go
- Stars
- 305
- Forks
- 46
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from slackapi/slack-cli
-
Installer aborts on an existing same-named `slack` binary; prefer install + warning over hard abort Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug build release
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
area:bolt-python bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
build code health
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
enhancement semver:minor
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in slackapi/slack-cli
Similar issues
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
JakeChampion/lang#10213 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100