You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2022. It is now read-only.
I confirm that this is a feature request rather than a question.
What problem does this feature solve?
Systems can be deployed to more than one physical location and it would be nice to be able to say that the API is affected, but might only be affected in SFO vs NYC.
Defining this as a subsystem allows for a non-location base subsystem to be affected.
What does the proposed API look like?
Not sure it applies.
How should this be implemented in your opinion?
YAML arrays of some sort maybe.
- affectedsystems:
- CDN: [NYC, SFO]
OR
- affectedsystems:
- API:
- SFO
- DEN
Are you willing to work on this yourself?**
Yes.
The text was updated successfully, but these errors were encountered:
Hi @ekristen. Thank you for opening this issue. We're evaluating the best and simplest way to implement this. When we get a solution, we'll let you know 🤓 .
Feature request
What problem does this feature solve?
Systems can be deployed to more than one physical location and it would be nice to be able to say that the
API
is affected, but might only be affected inSFO
vsNYC
.Defining this as a subsystem allows for a non-location base subsystem to be affected.
What does the proposed API look like?
Not sure it applies.
How should this be implemented in your opinion?
YAML arrays of some sort maybe.
OR
Are you willing to work on this yourself?**
Yes.
The text was updated successfully, but these errors were encountered: