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
The OCF Resource Agent Developer Guide at http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html states that "An OCF compliant resource agent can be implemented in any programming language. The API is not language specific. However, most resource agents are implemented as shell scripts, which is why this guide primarily uses example code written in shell language."
The current implementation of the ocf-tester invokes the tested ra script with constructs like (eg line 214):
bash /path/to/resourceagent validate-all | cd /usr/share/resource-agents && $METADATA_LINT)
Presumably this should be something more like:
(/path/to/resourceagent validate-all) | cd /usr/share/resource-agents && $METADATA_LINT)
To remove the assumption that the resource agent is implemented in sh or bash.
The text was updated successfully, but these errors were encountered:
If bash is not necessary, then why does the command "ocf-tester" break when invoked with resource agents that are implemented in anything other than bash?
The OCF Resource Agent Developer Guide at http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html states that "An OCF compliant resource agent can be implemented in any programming language. The API is not language specific. However, most resource agents are implemented as shell scripts, which is why this guide primarily uses example code written in shell language."
The current implementation of the ocf-tester invokes the tested ra script with constructs like (eg line 214):
Presumably this should be something more like:
To remove the assumption that the resource agent is implemented in sh or bash.
The text was updated successfully, but these errors were encountered: