Skip to content

[defect] OCF needs exact lexical rules #19

@jnpkrn

Description

@jnpkrn

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions