Onboard the Eastern Idaho Info Exchange as an info-exchange tenant once their group settles on a name and domain.
This is the original ask from #269. That issue has been re-scoped to deliver the platform-wide info-exchange support (using EWYAIX as the first concrete onboarding); this issue tracks the E Idaho-specific work that follows.
Scope
Once their group settles on a name and domain:
- NAC registers an
EIDIX-style slug in the AFP centers API, with platforms matching an info exchange (forecasts: false, weather: false, warnings: false, stations: true, obs: true).
- Add the new slug to
AVALANCHE_CENTERS in src/utilities/tenancy/avalancheCenters.ts with their real domain as customDomain.
- Run
provisionTenant for the new slug.
- Production DNS cutover at launch (same playbook as any tenant launch).
Dependencies
Context
Per @rustynwac in #269: E Idaho will come online "between now and the fall" (~Aug-Oct 2026), grant-funded.
Onboard the Eastern Idaho Info Exchange as an info-exchange tenant once their group settles on a name and domain.
This is the original ask from #269. That issue has been re-scoped to deliver the platform-wide info-exchange support (using EWYAIX as the first concrete onboarding); this issue tracks the E Idaho-specific work that follows.
Scope
Once their group settles on a name and domain:
EIDIX-style slug in the AFP centers API, with platforms matching an info exchange (forecasts: false, weather: false, warnings: false, stations: true, obs: true).AVALANCHE_CENTERSinsrc/utilities/tenancy/avalancheCenters.tswith their real domain ascustomDomain.provisionTenantfor the new slug.Dependencies
Context
Per @rustynwac in #269: E Idaho will come online "between now and the fall" (~Aug-Oct 2026), grant-funded.