opsworkscm_disassociate_node: Disassociates a node from an AWS OpsWorks CM server, and...

View source: R/opsworkscm_operations.R

opsworkscm_disassociate_nodeR Documentation

Disassociates a node from an AWS OpsWorks CM server, and removes the node from the server's managed nodes

Description

Disassociates a node from an AWS OpsWorks CM server, and removes the node from the server's managed nodes. After a node is disassociated, the node key pair is no longer valid for accessing the configuration manager's API. For more information about how to associate a node, see associate_node.

See https://www.paws-r-sdk.com/docs/opsworkscm_disassociate_node/ for full documentation.

Usage

opsworkscm_disassociate_node(ServerName, NodeName, EngineAttributes = NULL)

Arguments

ServerName

[required] The name of the server from which to disassociate the node.

NodeName

[required] The name of the client node.

EngineAttributes

Engine attributes that are used for disassociating the node. No attributes are required for Puppet.

Attributes required in a DisassociateNode request for Chef

  • CHEF_ORGANIZATION: The Chef organization with which the node was associated. By default only one organization named default can exist.


paws.management documentation built on Sept. 12, 2024, 6:19 a.m.