ACMS-3647: Add helper function to get segmented Acquia environment names. #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rajeshreeputra
force-pushed
the
ACMS-3417
branch
2 times, most recently
from
57493bf to
aad2999
Compare
rajeshreeputra
changed the title
|
I'm happy to merge this if you get tests passing. |
rajeshreeputra
force-pushed
the
ACMS-3417
branch
from
2b46cb1 to
b341267
Compare
All tests are passing now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #ACMS-3647
Motivation
Currently environment detector does not group the environments, hence proposed new method to group it.
Proposed changes
Segment the environments, like below:
prodor01live, segmented byprodstage,test,stg,01test, segmented bystagedev,01dev, segmented bydevode01,ode02,ode.., segmented byodeAlternatives considered
How else could the original issue / use case be addressed? Why did you choose this solution over any others?
Testing steps
How can we replicate the issue and verify that this PR fixes it?