When using a configuration management tool (Puppet, Chef) it is essential to make all configuration changes idempotent and to know if an actual configuration change was made or it was a no-op.
When using Wildfly CLI, when I try for example to set a same value twice:
[standalone@embedded /] :write-attribute(name=organization, value=value1)
{"outcome" => "success"}
[standalone@embedded /] :write-attribute(name=organization, value=value1)
{"outcome" => "success"}
I don't see any feedback for the second command that the value is already there and that it was a no-op.
Is it possible to achieve this with Wildfly CLI?
It wasn't a no-op. You told it to write and it did write. A write happens regardless of the value, assuming the value is valid and the attribute is writable.
--
James R. Perkins