add "user input" to custom attributes that are added to custom service shells

Hi @Yoav.E,

Please check the below from the DevGuide https://devguide.quali.com/shells/8.3.0/customizing-shells.html, I'm copying here:

To publish a service shell’s attribute:

1) Add or modify an existing attribute as explained in the Customizing a Shell’s attributes section above.

2) If you want the service’s attribute to be exposed in the blueprint and sandbox, replace the tags line with the following:

tags: [user_input]

3) Save the shell-definition.yaml file, package and import the shell into CloudShell.

Hi Maya,

the process you mentioned above works for attributes I add via the shell-definition.yaml.

that is what I've ended up doing for my case...

in the Idea , I am talking about custom attributes (the non-namespaced kind), because the same attribute applies to a few different second-gen custom service shells.

right now this option exists for second-gen custom service shells , but is unusable because I can't see that attribute anywhere outside of the API.

thanks,

Yoav

Thanks Yoav. Could you please provide more information about what you're using this for, so I can get a sense of the use case? Or is the main issue that this option is still visible and only relevant to 1st gen (i.e. perhaps needs be removed)?

Hi Maya,

I needed it when adding an attribute to a few service shells and I didn't want to add the attribute individually to each custom shell. I was able to workaround (as was discussed in the previous comments) it but it meant triple work on that case.

I think that option for service shells makes sense and should be there, but without the user input flag it is not going to bring much value, as the user or admin can't interact with it (read, write, update or even see it exists) outside of the API.

thanks,

Yoav

Hi, I'm happy to update this idea is in our backlog and planned for upcoming CloudShell releases.

Hi I'm happy to update that this idea is included in CloudShell 9.2