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
When a service account is create via the rhoas service-account create command, it's possible to provide a so called description via the --short-description parameter.
When we use the rhoas service-account describe command, such an information is reported back as name field in the JSON and not as description.
Isn't it better to be consistent across them. I think that the name field would be much better as option in the creation command insted of the short description imho.
The text was updated successfully, but these errors were encountered:
Sorry to be precise, I think that name' in the json is totally right. I think that --short-descriptionis bad and should be--name` on creation to be consistent.
reintroduce name, but keep --short-description as alias
add description to short description (flagging that api field will be present as name
So while we not going to fix the core issue I think we can do nr2 easily (it is only content change)
Benefit of that will be that we going to have this in the CLI and documentation resolving confusion around this.
When a service account is create via the
rhoas service-account create
command, it's possible to provide a so called description via the--short-description
parameter.When we use the
rhoas service-account describe
command, such an information is reported back asname
field in the JSON and not as description.Isn't it better to be consistent across them. I think that the
name
field would be much better as option in the creation command insted of the short description imho.The text was updated successfully, but these errors were encountered: