xattr module updates - #12048
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
|
Note that Edit: ah, wait - more like 2.5 years, when we stop supporting ansible-core 2.21... |
This comment was marked as outdated.
This comment was marked as outdated.
russoz
left a comment
There was a problem hiding this comment.
Hi @bcoca Thanks for the improvement!
Got a couple of comments there, there's obviously the changelog frag, and a comment for future PRs: states read, all, keys should be transposed to a new module xattr_info and deprecated from here.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
| type: bool | ||
| default: true | ||
| notes: | ||
| - Starting with community.general 13.0.0 this action no longer requires the xattr CLI tools installed on the target. |
There was a problem hiding this comment.
13.0.0 is being released in less than 24h - this may need adjusting if we merge after that.
Unless @felixfontein wants to wait for it.
There was a problem hiding this comment.
instead of continually updating it, lets just do so when out of draft and ready to merge
- now uses system calls instead of shelling out this should make it more usable (no CLI needed), less fragile (no scrape!) and speed it up (no shell/fork) - moved to case statement - ensure we have message and result in all cases - state read w/o key now issues a warning, it works as state == all TODO: - changelog - tests Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com>
This comment was marked as outdated.
This comment was marked as outdated.
|
Right now the tests are failing, so I guess it's not LGTM yet :) |
|
"LGTM" ;-) |
SUMMARY
TODO:
ISSUE TYPE
COMPONENT NAME
module xattr
ADDITIONAL INFORMATION