Skip to content

[CI only, fork-internal] feat(teams): provision tenants on installation updates - #4

Draft
jchu96 wants to merge 8 commits into
contrib/teams-adapterfrom
contrib/teams-install-flow
Draft

jchu96 wants to merge 8 commits into
contrib/teams-adapterfrom
contrib/teams-install-flow

Conversation

@jchu96

@jchu96 jchu96 commented Sep 23, 2026

Copy link
Copy Markdown
Owner

Fork-internal draft to run CI on contrib/teams-install-flow @ 9b2f114 (stacked on contrib/teams-adapter @ 5bdc726, the head of pymc-labs#220). Not for merge here; the upstream PR follows pymc-labs#220.

Follow-up to pymc-labs#220's Identity section and caveat 6: the Bot Framework installationUpdate activity provisions the tenant.

  • add / add-upgrade / SDK upgrade provision idempotently (pending first, ready after defaults reconcile), welcome once; open enrollment by default, DAIMON_TEAMS__ALLOWED_TENANT_IDS closes it with a polite decline.
  • remove / remove-upgrade archive the tenant only for team or group-chat installs; a personal-scope uninstall never archives the organisation tenant.
  • Message resolution admits any provisioned, ready, unarchived tenant (no longer pinned to the bot registration tenant).
  • Upgrade action tags are normalised before SDK parsing so they reach the handler instead of failing validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant