Write-attribute: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
Sets the value of an attribute for the selected resource. The value may be null if the underlying model supports null values. | Sets the value of an attribute for the selected resource. The value may be null if the underlying model supports null values. | ||
If the attribute does not exist, but it is a known attribute to the management resource, it is created and assigned to the given value. | If the attribute does not exist, but it is a ''known attribute'' to the management resource, it is created and assigned to the given value. | ||
If the attribute does not exist and it is not a known attribute to the management resource, the operation fails with <tt>"outcome" => "failed"</tt> and description "JBAS014792: Unknown attribute ..." | If the attribute does not exist and it is not a known attribute to the management resource, the operation fails with <tt>"outcome" => "failed"</tt> and description "JBAS014792: Unknown attribute ..." | ||
Revision as of 03:57, 16 November 2016
Internal
Overview
Sets the value of an attribute for the selected resource. The value may be null if the underlying model supports null values.
If the attribute does not exist, but it is a known attribute to the management resource, it is created and assigned to the given value.
If the attribute does not exist and it is not a known attribute to the management resource, the operation fails with "outcome" => "failed" and description "JBAS014792: Unknown attribute ..."
If the attribute exists, the current value is overwritten.
Syntax
:write-attribute(name="...",value="...")
Use Cases
Removing an Attribute
:write-attribute(name=socket-binding)
socket-binding will be removed from the current node.
If the management resource is listed in CLI, the "removed" attribute shows as "undefined":
... socket-binding=undefined ...