CFE-4529: Added docs for policy function getacls()#3454
Conversation
Ticket: CFE-4529 Signed-off-by: Lars Erik Wik <lars.erik.wik@northern.tech>
| - `path` : Absolute path to file or directory | ||
| - `type` : In the range `(access|default)` | ||
|
|
||
| **Example:** |
There was a problem hiding this comment.
Maybe you could use the docs macro to include the example you have created in the other PR like it has been done for other functions
For example:
Example:
[%CFEngine_include_snippet(isreadable.cf, #+begin_src cfengine3, .*end_src)%]
Output:
[%CFEngine_include_snippet(isreadable.cf, #+begin_src\s+example_output\s*, .*end_src)%]
| "access_acls" | ||
| string => getacls("/tmp/bar", "access"); | ||
| } | ||
| ``` |
There was a problem hiding this comment.
It would be nice to show the expected output (you can add it to getacls.cf, cf. my previous comment)
There was a problem hiding this comment.
Agreed that it would be nice to show the expected output.
But, then you need to be able to make sure you know what the result will be for whatever system doc build happens on.
There was a problem hiding this comment.
Probably won't be so easy given that ACLs are not supported on all platforms and file systems
|
@cf-bottom jenkins |
|
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/fast-build-and-deploy-docs-master/135/ Documentation: http://buildcache.cfengine.com/packages/build-documentation-pr/jenkins-fast-build-and-deploy-docs-master-135/output/_site/ |
5 participants
No description provided.