The "app link" command is limited to one app per environment per team
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by tracing the app link command and its saved-app behavior, then review the linked app-link documentation and the reported slack deploy selection flow. Confirm how team, environment, and app IDs are currently represented. Done means multiple apps can be retained and selected for later deployments without the current overwrite error.
Written by the indexing model from the issue text.
Description
Description
The app link command is limited to one app per environment (local or deployed) per team, which limits the development "stages" that might exist:
- Development
- Staging
- Production
At the moment this is expected behavior:
Only one app can exist for each combination of Team ID and environment.
📚 https://docs.slack.dev/tools/slack-cli/reference/commands/slack_app_link/
Version
Using slack v3.10.0
Steps to reproduce:
- Create multiple apps for a team on api.slack.com/apps
- Run the
app linkcommand in a project using these app IDs - Find that one app can exist for development purposes
Expected result:
Multiple apps to be saved for later selections:
$ slack deploy
? Select an app
A0101010101 slackbox-ez T0000000001 (production)
> A0000000001 tinyspeck T0123456789 (production)
A0123456789 tinyspeck T0123456789 (staging)
Actual result:
$ slack app link
...
🚫 A saved app was found and cannot be overwritten (app_found)
💡 Suggestion
Remove the app from this project or try again with --force
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 carvel-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
carvel-dev/kapp-controller#1861 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100