puppet-retrospec | generate puppet code tests modules facts types | Configuration Management library
kandi X-RAY | puppet-retrospec Summary
kandi X-RAY | puppet-retrospec Summary
Proper testing is hard especially when you are new to ruby, rspec or even puppet. Retrospec makes it dead simple to get started with advanced puppet module development. Retrospec will scan you puppet module files and actually write some very basic rspec-puppet test code. Thus this gem will retrofit your existing puppet module with everything needed to get going with puppet unit testing. Additionally, retrospec will outfit your module with any file you can think of. Say goodbye to repetitive module setup. Not only will retrospec generate tests for you, it will also assist in creating many of the advanced puppet module files like custom facts, functions, types, providers and schemas, as well as their associated test files. It will even create the module from scratch if so desired. The project was named retrospec because there are many times when you need to retrofit your module with various things.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Ensure the module is valid
- This method returns a list of all files that should be included in the provider .
- Create AST for AST .
- = begin Function to create a module directory
- Returns the path to the templates directory
- Create a temporary module directory
- returns the type file if it exists
- Creates a puppet request object
- This method returns the list of sources for the template file .
puppet-retrospec Key Features
puppet-retrospec Examples and Code Snippets
Community Discussions
Trending Discussions on Configuration Management
QUESTION
I have a requirement where I need to check for a file on the puppet master and copy it to the agent only if it is not empty.
I have the following so far:
...ANSWER
Answered 2020-Dec-17 at 02:50You cannot use an Exec resource to perform the check, because you need to perform the evaluation during catalog building, and resources are not applied until after the catalog is built. Moreover, the test command tests for the existence of a the specified path. It does not know about URLs, and even if it did, it would be unlikely to recognize or handle the puppet: URL scheme. Furthermore, there is no association whatever between resource titles and variable names.
To gather data at catalog building time, you're looking for a puppet function. It is not that hard to add your own custom function to Puppet, but you don't need that for your case -- the built-in file() function will serve your purpose. It might look something like this:
QUESTION
So for a hobby project of mine, I would like to create an application that translates an HTTP call and request between two services.
The application does that based on a configuration that can be set by the user. The idea is that the application listens to an incoming API call translates the call and then forwards it.
Then the application waits for a response then translates the response and sends it back to the caller.
A translation can be as simple as renaming a field value in a body object or replace a header field to the body.
I think a translation should begin with mapping the correct URL so here is an example of what I was thinking of a configuration should look like:
...ANSWER
Answered 2020-Nov-10 at 11:42I have done something sort-of-similar in a different context (generate code from an input specification), so I will provide an outline of what I did to provide some food for thought. I used Config4* (disclosure: I developed that). If the approach I describe below is of interest to you, then I suggest you read Chapters 2 and 3 of the Config4* Getting Started Guide to get an overview of the Config4* syntax and API. Alternatively, express the concepts below in a different configuration syntax, such as XML.
Config4* is a configuration syntax, and the subset of syntax relevant to this discussion is as follows:
QUESTION
I have written separate playbooks for tomcat deployment on both Ubuntu and Linux as well, instead of mentioning **
when: ansible_distribution == 'Ubuntu'
**in every line in the playbook, i want to run the whole playbook only when this condition meets.
This is my code
...ANSWER
Answered 2020-Feb-10 at 14:44Q: "I want to run the playbook only on the hosts based on the ansible_distribution."
A: It's not possible to include a playbook. This would run the playbooks recursively.
Only import of a playbook is available. Moreover import_playbook is not a task. It's simply a tool to modularize large playbooks with multiple plays.
Ansible conditionals do not apply to import_playbook the same way as they do not apply to playbooks.
Instead, it is possible to create a group that will be used in the playbook.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install puppet-retrospec
This will also install the retrospec framework that is required to use the plugin.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
