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
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=E12345that would search their .credentials file for an auth token for that enterprise ID, update their local apps.json and reinstall at the org levelCurrently, the manual intervention required is to
slack loginto the new enterprise team which will save the new auth in your~/.slack/credentials.jsonfile, then update the local.slack/apps.jsonfile in the project to reflect the new enterprise team ID (app ID remains the same as before the migration). Sample below:🤞 Run
slack deployand if the contents of.slack/apps.jsonare valid, you should be able to select the app and re-deployRequirements