This example request includes usage of the following Chef products (select one
or more):
[x] Chef Automate
Includes Chef Infra Server, Chef Infra Client, Chef Workstation and Supermarket
[ ] Chef Workstation
Includes Chef Workstation only
[ ] Habitat
Includes Habitat, Habitat Builder (on-prem and SaaS)
[ ] InSpec
Includes InSpec, Ad-hoc Automate jobs, Audit Cookbook
Problem Statement
Currently, if a node is deleted from a Chef Infra Server, and there is a backup of that node via knife ec backup, the node can be restored using knife node from file my_node.json, however, the permissions for the node to access it's own node object are not restored and must be manually done by granting permissions to itself via Chef Manage. This is not an automated way of restoring a node, there are most likely API calls or knife raw commands that can be used to restore the proper permissions as well as the node object itself. This example would show how to do that.
Example Request
This example request includes usage of the following Chef products (select one or more):
Problem Statement
Currently, if a node is deleted from a Chef Infra Server, and there is a backup of that node via
knife ec backup, the node can be restored usingknife node from file my_node.json, however, the permissions for the node to access it's own node object are not restored and must be manually done by granting permissions to itself via Chef Manage. This is not an automated way of restoring a node, there are most likely API calls orknife rawcommands that can be used to restore the proper permissions as well as the node object itself. This example would show how to do that.External References
Additional Notes