This repository has been archived by the owner on Jun 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 197
Consider Supporting Subsystems #162
Labels
Milestone
Comments
Thanks for opening this issue, a maintainer will get back to you shortly! Be sure to follow the issue template! 🤓 |
Hey @ekristen 👋, Thank you for opening an issue. Check out our OpenCollective and consider backing us. Help us to continue developing this Amazing Project, we will appreciate it ❤️. You can contribute from $2 🤓, less than a cup of coffee ☕ 😃 https://opencollective.com/statusfy PS.: We offer |
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 🤓 . |
hello all. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: