Visualize the name of the configuration

[giannidallatorre]

When you create a new deployment from the Application repository page, the first indication is:
Select configuration but there is no indication of the name of the configuration.

I understand, most of the time, is more understandable visualizing the cloud provider and the associated deployment parameters, but the actual status is quite confusing.
It would clearer, if the portal showed also the name of the configuration (including the underlying composition).

Alternatively, we can change the way the configurations are displayed, putting less stress on the name of the configuration (that in this moment is completely useless) and stressing more the combination of his components (cloud provider - and deployment parameter), in order to match the behaviour of the portal during the deployment.

[jadianes]

Actually what is shown is:
Configuration name | @(Cloud provider name) Cloud provider type

[giannidallatorre]

Sorry, you are right, actually I have Configuration name with the same name of Deployment parameters name.

Maybe my set up it is not so common and therefore it is me that I am confused!
Anyhow I would still suggest to show all 3 information. Maybe with Configuration name in bold and the rest smaller.

When you want to change a parameter the workflow is:

1. Note the name of the configuration
2. Navigate to profile*
3. Look for the specific configuration**
4. Note the name of the Deployment parameter
5. Navigate to Deployment Parameters tab
6. Look for the specific Deployment Parameters **
7. Edit the the configuration

This would save a couple of steps (especially requiring just to memorize one name instead of two, that for people like me is a huge improvement!).

Using the portal, it is quite common to modify the deployment configuration, while is not that common to modify the configuration once is set up.

• which is not that logically related to a configuration
  ** possibly scrolling because we display se only see 2-3 per page

[jadianes]

Yes, it is quite clumsy process right now, I agree. Some sort of direct access to each entity would help as well. But the problem right now is also that there is a common Profile page with tabs for everything. Maybe if we split that into Profile, Configurations, Cloud Providers, and Deployment Parameters, and then provide direct access from the selection to add new or edit...

In any case editing these items is not something a normal user would do, specially not the deployment parameters. But who knows what real users think??

[giannidallatorre]

+1 for the Idea to move away Configurations and Deployment Parameters from Profile.
I can understand instead Cloud Providers there and in the future I maybe an SSH key section.

[jadianes]

Yes, the SSH key section is something we are planning to do at some point, so they can be reused/selected instead of adding them every time a deployment is triggered.

…

On 21 December 2017 at 12:05, Gianni Dalla Torre ***@***.***> wrote: +1 for the Idea to move away Configurations and Deployment Parameters from Profile. I can understand instead Cloud Providers there and in the future I maybe an SSH key section. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAqQJnpE_3hpzhPbJSKdkSZHN6SNpaiGks5tCkmlgaJpZM4RJmPi> .