Provide a CLI command for updating an app after a grid migration
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with the existing slack login and slack deploy entry points, then trace how ~/.slack/credentials.json and .slack/apps.json are read and updated. Define the migration command around an app ID and enterprise ID, and verify that it selects the enterprise token, updates the local app mapping, and enables a subsequent deploy.
Written by the indexing model from the issue text.
Description
Description
Coded workflow (Deno) apps installed to a standalone workspace that later gets migrated to an enterprise grid currently need manual intervention to continue working with the CLI. Maybe we want to add a new command like slack app migrate --app=A1234 --enterprise-id=E12345 that would search their .credentials file for an auth token for that enterprise ID, update their local apps.json and reinstall at the org level
Currently, the manual intervention required is to slack login to the new enterprise team which will save the new auth in your ~/.slack/credentials.json file, then update the local .slack/apps.json file in the project to reflect the new enterprise team ID (app ID remains the same as before the migration). Sample below:
{
"apps": {
"E12345678": {
"app_id": "A12345678",
"enterprise_id": "E12345678",
"team_domain": "my-domain",
"team_id": "T98765432"
}
},
"default": "my-domain"
}
🤞 Run slack deploy and if the contents of .slack/apps.json are valid, you should be able to select the app and re-deploy
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
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100