-
-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow grouping of servers by stage/environment #65
Comments
That's a great suggestion. Thanks for sharing! I'm not going to add anything to the spec in the short term but I'll take into account for future features. Anyone interested in this feature, please upvote it so that I know if this is something urgent or not. |
Slightly different, but similar issue. Besides the |
@lwielek that's an interesting approach to consider too. Would you mind creating a proposal? |
@fmvilas
|
Sorry, I meant creating a separate issue as the problem is different. As part of the proposal, I'd like to understand:
Thanks! |
Thanks, @lwielek! Great job describing the feature. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity 😴 |
This issue has been automatically marked as stale because it has not had recent activity 😴 |
This was solved by #654 |
It is common to have many servers for the same stage (dev, test, acc, ..), the variable substitutions into the server object can help but the substitution can also be problematic when there is some restriction on what can be substituted.
A solution is to create different servers however, there is nothing to group them and to restrict the usage of servers from different stages.
I can be interesting to have a
group
attribute in server:Configuration:
Current:
Proposal:
The text was updated successfully, but these errors were encountered: