Is your feature request related to a problem? Please describe.
Multi-tenant users are frustrated when it is difficult to disambiguate different APIProducts owned by separate teams when they are targeted at a single Environment. Portal needs to offer a strictValidation setting on Environments. This would cause the controller to verify that there are no conflicts across separate APIProducts (that might be owned by separate, independent project teams) within an Environment. These can lead to duplicate routes that result in short-circuiting and possibly other confusing behaviors. Status for strict-validation Environments should be reported in the Environment status.
Describe the solution you'd like
Portal needs to offer a strictValidation setting on Environments to detect conflicts. Status for strict-validation Environments should be reported in the Environment status.
Is your feature request related to a problem? Please describe. Multi-tenant users are frustrated when it is difficult to disambiguate different APIProducts owned by separate teams when they are targeted at a single Environment. Portal needs to offer a
strictValidation
setting on Environments. This would cause the controller to verify that there are no conflicts across separate APIProducts (that might be owned by separate, independent project teams) within an Environment. These can lead to duplicate routes that result in short-circuiting and possibly other confusing behaviors. Status for strict-validation Environments should be reported in the Environment status.Describe the solution you'd like Portal needs to offer a
strictValidation
setting on Environments to detect conflicts. Status for strict-validation Environments should be reported in the Environment status.Additional context See related issue #141