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
What's the user value of this feature request?
The user value is that he will see a clear list of the binded applications only once when looking at the service details (cf service ) and not multiple times for every shared space.
In our case, we have a shared instance with about 40 binded applications and we shared it with ~10 spaces. So, it's not manageable to view so many binded applications in one view.
Who is the functionality for?
Developers and operators who use the CF CLI and need to share their instance with other CF spaces.
How often will this functionality be used by the user?
The usage of this feature is based on the user's tasks, but in general, whenever the user would like to share the instance with other spaces and see the service detailed.
Who else is affected by the change?
This feature doesn't cause a breaking change. No other users affected by this change.
Is your feature request related to a problem? Please describe.
The problem is that binded applications of shared instances are shown on the binded apps list of the service instance.
When sharing the instance in N spaces , the binded apps list is duplicated N times.
See attached file for result of "cf service portal-dynatrace" cmd in lts space where portal-dynatrace service instance is shared with 6 spaces. cf service portal-dynatrace in lts.txt
Describe the solution you'd like
The expectation is that when viewing the details of the service in the main space, only its binded application will appear. A new environment variable will be added to specify the space that the user would like to see its binded applications.
Describe alternatives you've considered
We see no other alternative solution.
Additional context
N/A
Note:
As of the GA of the v7 CLI, the v6 line is no longer under active development and will be updated only to patch CVEs or fix severe blocking defects with no workarounds.
The text was updated successfully, but these errors were encountered:
What's the user value of this feature request?
The user value is that he will see a clear list of the binded applications only once when looking at the service details (cf service ) and not multiple times for every shared space.
In our case, we have a shared instance with about 40 binded applications and we shared it with ~10 spaces. So, it's not manageable to view so many binded applications in one view.
Who is the functionality for?
Developers and operators who use the CF CLI and need to share their instance with other CF spaces.
How often will this functionality be used by the user?
The usage of this feature is based on the user's tasks, but in general, whenever the user would like to share the instance with other spaces and see the service detailed.
Who else is affected by the change?
This feature doesn't cause a breaking change. No other users affected by this change.
Is your feature request related to a problem? Please describe.
The problem is that binded applications of shared instances are shown on the binded apps list of the service instance.
When sharing the instance in N spaces , the binded apps list is duplicated N times.
See attached file for result of "cf service portal-dynatrace" cmd in lts space where portal-dynatrace service instance is shared with 6 spaces.
cf service portal-dynatrace in lts.txt
Describe the solution you'd like
The expectation is that when viewing the details of the service in the main space, only its binded application will appear. A new environment variable will be added to specify the space that the user would like to see its binded applications.
Describe alternatives you've considered
We see no other alternative solution.
Additional context
N/A
Note:
As of the GA of the v7 CLI, the v6 line is no longer under active development and will be updated only to patch CVEs or fix severe blocking defects with no workarounds.
The text was updated successfully, but these errors were encountered: