have the option to hide some of the family attributes inherited from the standard

Hi Yoav

You can override the standard shell attributes (including their rules) by specifying them in your shell YAML file with tags definition.

More information can be found here:

https://qualisystems.github.io/devguide/shells/8.3.0/modeling-the-shell.html

Hi Meni,

I still can't change this to hide "Family" attributes , only "Model" attributes.

so it does not help me in this case.

thanks,

Yoav

I have this problem, and I am not allowed to change the family attributes either.

For instance "System Name" and "Contact Name" I do not need from the generic resource. They show up in the blueprint model. If I try to override them to make them invisible in the YAML definition I get the error "Can not override family attributes".

Changing family attributes is not a good idea, as it affects all the shells associated with the family.

It may also break shells that expect these attributes (for example: Quali's out-of-the-box shells).

I think that most users will prefer to have unused attributes.

changing the setting rule for an attribute will only hide it , not make it non-existent.

so it will not break any existing shell.

there is no way to remove an attribute completely, even for model attributes, which I agree can be risky.

please remove the "exists" tag from this idea , as it does not exist.

thanks,

Yoav

Yoav

You can certainly affect the behavior of an attribute in a way that breaks the shell.

i.e - making it admin only, removing it from auto load.

It is ok to change your shell - by changing the model attributes, but as I said changing the family attribute will affect other shells (including out-of-the-box shells). therfore, this feature is not planned.

Hi Meni,

I still can't see how changing the Setting\Configuration rule can do any harm to the functionality or usabilty of any shell , even to the out-of-the-box shells.

you can limit the changes to that to meet the real need that comes from this idea.

and please remove the "exists" tag from this idea , as it does not exist.

thanks,

Yoav

Hi,

I want to summarize for anybody who may be interested in this:

• Overriding standard shell attributes (model level) - feature already exists: https://qualisystems.github.io/devguide/shells/8.3.0/modeling-the-shell.html

• Overriding standard shell attributes (family level) - feature not planned. Reason: a family (by definition) contains multiple shells, allowing one shell to change the family may lead to unexpected behavior for other shells.

Hi Meni,

I'm not sure what you mean by overriding? The link you point to only shows how to override a default value, not how to override an existing attribute. I don't want to change the family, I want to change the "inherited" attribute in the shell I derived from the family. When overriding an attribute in my own shell:

Error: Failed to update shell. CloudShell responded with: 'Error: The shell package is invalid: Cannot override family attribute(s) 'Vendor' in a shell.'

Overriding the attribute in my own shell does not need to impact any other shell so should be allowed.

Hi @mjuffermans@libertyglobal.com,

Any attribute that is on the family level can't be modified per shell. You can find more details about it in this article in the devguide, under "modifying existing attributes".

The reason we have attributes on the family level at all is to allow creating abstract resource which aren't model specific and filter according to some attribute, for example "I want a router in some location but I don't care which model I get". Once we raise an attribute to the family level it can't be edited per shell because the attribute is not associated with shell level anymore but instead with the family level (has a namespace of the family), and changing it will affect all other shells that use this family attribute.

Bottom line, in your case if you want a shell specific attribute please add a new attribute to your shell in the relevant level.

Hope this clarifies things,

Alona.