We are using the component modules puppetlabs/apache, puppetlabs/mysql, and mayflower/php, and encapsulating these into the profile classes web::apache database::mysql and programming::php, respectively. You can see that I have used some sensible subdirectories and class names to reflect their contribution to the stack, namely web, db, and programming subdirectory locations for the Apache, MySQL, and programming profiles, respectively.
Using subdirectories for sensible, readable profile class groups
by Jason Southgate, Ryan Russell-Yates
Mastering Puppet 5
- Title Page
- Copyright and Credits
- Dedication
- Packt Upsell
- Contributors
- Preface
- Authoring Modules
- Using a decent IDE and plugins
- Using good module and class structure
- Using the new Puppet Development Kit commands
- Validating your module
- Unit testing your module
- Staying on the lookout for code smells
- Working with dead code
- Using Puppet Forge
- Working with the community
- Writing great documentation
- Adding module dependencies
- Adding compatibility data for your modules
- Using the new Hiera 5 module level data
- Summary
- Roles and Profiles
- Summary of the pattern
- Profiles
- Profiles best practices summary
- Designing for use of the include keyword
- Using subdirectories for sensible, readable profile class groups
- Hiding complexity with parameters, defaults, and abstraction
- Deciding how to set the parameters for component classes
- Deciding to use either automatic class parameter lookup or the lookup function
- Profiles best practices summary
- Roles
- Summary
- Extending Puppet
- Custom facts
- Custom functions
- Types and providers
- Types
- Creating and distributing the type
- Adding the namevar special attribute
- Adding additional type properties
- Adding the optional ensure property
- Adding type parameters
- Setting property and parameter defaults
- Checking the input value with a validate block
- Checking the input value against a newvalues array
- Checking datatype compatibility with munge
- Using autorequire for implicit relationships
- Using arrays to assign a list of values to an attribute
- Using the desc method to add inline documentation
- Providers
- Types
- Summary
- Hiera 5
- Separation of concerns between code and data
- Introducing a frame for the environment
- A more complete hierarchy
- Hiera 5 summary
- Global, environment, and module layers
- Encrypted YAML backend
- Lookup function
- Debugging Hiera
- Beyond Hiera using Jerakia
- Jerakia advanced use cases
- Installing Jerakia
- Configuring Jerakia
- Creating your default Jerakia policy
- Using Vault as an encryption backend
- Installing and configuring Vault
- Unsealing Vault
- Enabling the transit backend
- Creating an encryption key
- Creating a policy for encrypting and decrypting
- Checking the encryption is working correctly
- Allowing Jerakia to authenticate with our Vault
- Configuring Jerakia for encryption
- Encryption-enabling our Jerakia lookups
- Jerakia advanced use cases
- Summary
- Managing Code
- Workflow
- Continuous Integration
- Extending Puppet with Tasks and Discovery
- Exported Resources
- Application Orchestration
- Scaling Puppet
- Troubleshooting and Profiling
- Other Books You May Enjoy
Using subdirectories for sensible, readable profile class groups
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.