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

[defect] OCF needs exact lexical rules #19

Open
jnpkrn opened this issue May 9, 2018 · 1 comment
Open

[defect] OCF needs exact lexical rules #19

jnpkrn opened this issue May 9, 2018 · 1 comment

Comments

@jnpkrn
Copy link
Contributor

jnpkrn commented May 9, 2018

Currently, pacemaker seems to naively rely on some characters
never used in the name of the paramater to be passed to resource
agent, and would probably go south if that was the case.
However, OCF currently offers no such lexical assumptions.
We need to establish formal (hence predictable) grounds
in the specification in general, this one being low-hanging fruit
with significant impact, but the subtask would be to review
which other places are likewise not covered.

@jnpkrn
Copy link
Contributor Author

jnpkrn commented May 9, 2018

As demonstrated in
#15 (comment)
na(t)ive shell approach to environment variables also makes using
some characters in the parameter names basically frowned upon.

We have a benefit of considering these practical use cases now to restrict
lexical rules sensibly.

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

1 participant