Puppet Enterprise 2016.5
- Overview
- Release notes
- Puppet platform documentation
- Quick start guides
- Managing Windows nodes
- Installing
- System requirements
- What gets installed where?
- Downloading PE and installing overview
- Web-based installation: monolithic
- Text-mode installation
- Installing PE license key
- Installing Puppet agents
- Installing network device agents
- Installing compile masters
- Load balancing compile masters
- Installing ActiveMQ hubs and spokes
- Installing PE client tools
- Uninstalling PE
- PE and external PostgreSQL Setup
- Upgrading
- Migrating from 3.8
- Configuring PE
- Configuring high availability
- Monitoring infrastructure state
- Managing nodes
- Managing node requests
- Running Puppet on agent nodes
- Getting started with classification
- Grouping and classifying nodes
- Roles and profiles: Designing system configs
- Viewing node-specific information
- Making changes to node groups
- Removing nodes
- Preconfigured node groups
- How does inheritance work?
- Working with environments
- Node classifier service API
- Managing access
- Accessing the console
- Role-based access control
- Connecting PE with external directory services
- About RBAC permissions
- Creating and managing users and user roles
- Token-based authentication
- Running agents without root privileges
- RBAC service API v1
- RBAC service API v2
- Activity service API
- Managing applications
- Enforcing change with Puppet orchestrator
- Managing and deploying Puppet code
- Provisioning with Razor
- SSL and certificates
- Complete PE cert regeneration
- Individual PE component cert regeneration
- Regenerating a Puppet agent certificate
- Regenerating a compile master certificate
- Using an external certificate authority with PE
- Configuring the PE console to use a custom SSL certificate
- Custom Diffie-Hellman param file generation
- SSL for PE and external PostgreSQL
- APIs
- Managing MCollective
- Maintenance
- Troubleshooting
- Appendix
Error response description
Every error response from the Puppet orchestrator will be a JSON response. Each response will be an object containing the following keys:
kind: the kind of error encountered.msg: the message associated with the error.details: a hash with more information about the error.
For example, if an environment does not exist for a given request, an error is raised similar to the following:
{
"kind" : "puppetlabs.orchestrator/unknown-environment",
"msg" : "Unknown environment doesnotexist",
"details" : {
"environment" : "doesnotexist"
}
}