Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX: crm config informative check for an advertised parameter #1178

Open
zzhou1 opened this issue Apr 27, 2023 · 1 comment
Open

UX: crm config informative check for an advertised parameter #1178

zzhou1 opened this issue Apr 27, 2023 · 1 comment

Comments

@zzhou1
Copy link
Contributor

zzhou1 commented Apr 27, 2023

During an online conversation and we spent some amount of time to tell the subtle difference and which format is right or wrong for the following two usages:

a) less often usage

primitive p-lvmlockd lvmlockd \
     op start timeout=90 interval=0s \
     op_params syslog_priority=debug \
     op stop timeout=100 interval=0s \
     op monitor interval=30 timeout=90

b) the more common usage

primitive p-lvmlockd lvmlockd \
     params syslog_priority=debug \
     op start timeout=90 interval=0s \
     op stop timeout=100 interval=0s \
     op monitor interval=30 timeout=90

With some more digging and exercise, I see the tricky difference. params is at the primitive level which applies to all operations. While, op_params at the operation level, can be different among different operations.

To reduce the confusion and improve the user experience and efficiency, it would be nice to provide the following message and ask the user for manual confirmation for scenario a), for example,

"""
NOTICE: syslog_priority is an advertised parameter. Usually, it can be specified in params of primitive. However, it appears in op_params. Please double check. For more details, please refer to: crm configure help primitive
Do you still want to commit (y/n)?
"""

@zzhou1 zzhou1 changed the title UX: informative check for an advertised parameter UX: crm config informative check for an advertised parameter Apr 28, 2023
@liangxin1300
Copy link
Collaborator

@zzhou1
I see what you mean for the most.
BTW, what do you mean advertised parameter here? syslog_priority is a parameter, but it's not a mandatory one (no required=1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants