Map DA Site to Helix5 Site
- Dominant language
- JavaScript
- Stars
- 34
- Forks
- 71
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 29
Description
As an administrator I would like the ability to map a DA Site within an Org to a specific Edge Delivery Site in the Config Bus.
Currently there is a 1:1 relationship between DA Org/Site and Edge Delivery Org/Site. This does make sense to keep the Org 1:1, but a site should be able to be arbitrary.
---
I considered trying to use a lookup: Fetch all Sites from the Org config bus, and match the DA's context via the content path. However, this information currently requires a high-level of access (all config read) on the Edge Delivery side, resulting it a not-currently-viable option.
A config entry on the DA site to map to in the Edge Delivery system would work, but seems fragile.
Contributor guide
Research direction
No implementation file, test, or entry point is named. Start by tracing how DA Org/Site relationships are represented and how Edge Delivery Sites are resolved through the Config Bus, then determine a mapping approach that avoids all-config-read access. Done means a DA Site can map to an arbitrary Edge Delivery Site without breaking the existing 1:1 organization relationship.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100