You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we started working on the bot, we did not think there would be a web component. Eventually we put in the geolocate endpoint at which point we also included a web server.
A lot of the admin functionality ex: managing webhooks, incident drives etc. is managed in the Slack UI which is not optimal. Instead we should add an admin section to the bot that can be accessed through the web which allows you to do some basic admin functions that you currently do through the Slack UI.
Auth needs to be Google Auth scoped to CDS org.
The text was updated successfully, but these errors were encountered:
Propose adding the web UI to the Backstage instance as a plugin so that only the logic of the commands has to be handled (SSO, plugins permissions, etc. is baked into Backstage)
When we started working on the bot, we did not think there would be a web component. Eventually we put in the geolocate endpoint at which point we also included a web server.
A lot of the admin functionality ex: managing webhooks, incident drives etc. is managed in the Slack UI which is not optimal. Instead we should add an admin section to the bot that can be accessed through the web which allows you to do some basic admin functions that you currently do through the Slack UI.
Auth needs to be Google Auth scoped to CDS org.
The text was updated successfully, but these errors were encountered: