Ambassador SPIKE - Persist Layer IDs in GCZ Provider Config Automation
As a GCZ administrator, I want to run automatic configuration for GCZ Provider without losing layer ID persistence for layers/caches that have remained the same between config updates.
Concern: GCZ produces a single Feature Service. When config update is run, that same feature service will have layer ids swapped around.
Possible Solution:
- Update GCZ Provider to produce service per layer definition, so layer IDs would always be
1
and we wouldn't need to dynamically adjust them. Service names would be predictable.
Acceptance Criteria
- Direction decided on how layer id persistence may be supported