Create events on the shared outlook calendar from CSV input
curl -o go_asd_triage.sh https://raw.githubusercontent.com/ncsa/asd-triage-scheduler/main/go.sh
bash ./go_asd_triage.sh
./run.sh --help
./run.sh --list_teams
./run.sh --list_teams --start_at 7
./run.sh --mktriage --start 2023-03-01 --end 2023-04-01
(Note: existing triage meetings are maintained. This allows manual triage duty swaps directly in Outlook.)
./run.sh --mktriage --start 2023-04-01 --end 2023-05-01 --start_at 13
./run.sh --mkhandoff --start 2023-03-01 --end 2023-05-01
(Note: required attendees are imported from triage meetings.)
(Note: existing handoff meetings will be updated if membership doesn't match existing triage meetings.)
---
tenant_id: UofI tenant ID (from azure active directory)
client_id: client_id of custom app, registered in azure active directory)
client_secret: client_secret of custom app, registered in azure active directory)
scope:
- 'https://outlook.office365.com/Calendars.ReadWrite.Shared'
- 'https://outlook.office365.com/EWS.AccessAsUser.All'
Any path to a local, private file.
- https://portal.azure.com
- Login with UofI credentials
- App Registrations
- New Registration
- Supported account types
- Single tenant
- Supported account types
- New Registration
- View the new app
- Overview
- Copy "Client id" and "Tenant id" into "oauth config file" (above)
- API Permissions
- Microsoft Graph
- Calendars.ReadWrite.Shared
- EWS.AccessAsUser.All
- Microsoft Graph
- Authentication
- Redirect URIs
https://login.microsoftonline.com/common/oauth2/nativeclient
- Redirect URIs
- Certificates & Secrets
- New client secret
- Copy the secret into "oauth config file" (above)
- New client secret
- Overview