Steampunk Spotter

Trustable Automation

Ansible Playbook Platform that scans, analyzes, enhances, and provides insights for your playbooks.

Red hat partner
Mindpoint partner
Computer space partner
Computer space partner
Computer space partner
Computer space partner
Computer space partner
spotter reduce risks speed up automation image

Reduce risks and speed up automation

Optimize your automation with improved playbooks that guarantee reliable execution. Create and maintain Ansible Playbooks with ease while ensuring they are always up-to-date and secure.

  • identify hard-to-catch and time-consuming errors
  • improve quality, reliability and security of playbooks
  • reduce development and test time
  • follow automation best practices
Ansible automation platform

Supports Red Hat Ansible Automation Platform

Ansible versions

Checks all Ansible versions from 2.0 to 2.16

Spotter windows compatible

Windows compatible

What users say about Spotter

"Spotter transforms our automation process by identifying and mitigating potential issues before execution, reducing errors, and boosting productivity. It's not just a tool – it's a catalyst for revolutionizing how we manage and perceive automation."

Miguel Esteban,

CEO, Computer Space

"Spotter shines when it comes to writing new playbooks, following best practices and fixing errors in existing playbooks automatically. All in all, it saves so much time. It’s just easy as cake."

Andreas Hering,

System Engineer, Deutsche Telekom MMS

"Spotter can help my customers go from Ansible 2.9 to 2.13/14. It can help them find FQCN for modules, as they are having a hard time finding them, and can also help with any changed parameters. Spotter is easy to use and expand upon."

Jason,

Technical Account Manager

"Spotter found some things that other tools didn't, and I'm definitely adding it to my CI/CD pipeline."

Daniel Schier,

Consultant and DevOps Engineer

"Spotter is a game-changing tool that will revolutionize the way you manage your Ansible Playbooks. It's like having a personal playbook advisor!"

Sam,

Pythoholic

"Linter checks and corrections were a time-consuming job for our existing assets. We used Spotter to set up the development standards and best practices. I love that it shows errors that other available linters can't find. Spotter is awesome!"

Sagar Vispute,

Automation Developer

"Spotter is a great tool for all Ansible Playbook users. What I like most is that it finds version mismatches."

Sai Kartheek Dasari,

Senior Devops Engineer

"Spotter allows me to write perfect Ansible code without missing all the necessary arguments and delivers on the promise of helping with Ansible version upgrades."

Stéphane Robert,

DevOps Consultant

"Spotter is a very good addition to existing tools. Especially the tips and hints to migrate from older Ansible versions to current versions and the function to fix found errors are great!"

Sebastian,

System Engineer

"Spotter has allowed me to easily convert an Ansible role and many playbooks to be able to run on the latest Ansible versions. I'm excited to share this tool with my team and my company."

Matt,

Senior Infrastructure Engineer

"Ansible security scanning, assisted playbook writing, and custom policies functionalities of Steampunk Spotter greatly simplify and fast track my Ansible development experience."

Ioannis M.,

Solutions Architect

"Spotter transforms our automation process by identifying and mitigating potential issues before execution, reducing errors, and boosting productivity. It's not just a tool – it's a catalyst for revolutionizing how we manage and perceive automation."

Miguel Esteban,

CEO, Computer Space

"Spotter shines when it comes to writing new playbooks, following best practices and fixing errors in existing playbooks automatically. All in all, it saves so much time. It’s just easy as cake."

Andreas Hering,

System Engineer, Deutsche Telekom MMS

"Spotter can help my customers go from Ansible 2.9 to 2.13/14. It can help them find FQCN for modules, as they are having a hard time finding them, and can also help with any changed parameters. Spotter is easy to use and expand upon."

Jason,

Technical Account Manager

"Spotter found some things that other tools didn't, and I'm definitely adding it to my CI/CD pipeline."

Daniel Schier,

Consultant and DevOps Engineer

"Spotter is a game-changing tool that will revolutionize the way you manage your Ansible Playbooks. It's like having a personal playbook advisor!"

Sam,

Pythoholic

"Linter checks and corrections were a time-consuming job for our existing assets. We used Spotter to set up the development standards and best practices. I love that it shows errors that other available linters can't find. Spotter is awesome!"

Sagar Vispute,

Automation Developer

"Spotter is a great tool for all Ansible Playbook users. What I like most is that it finds version mismatches."

Sai Kartheek Dasari,

Senior Devops Engineer

"Spotter allows me to write perfect Ansible code without missing all the necessary arguments and delivers on the promise of helping with Ansible version upgrades."

Stéphane Robert,

DevOps Consultant

"Spotter is a very good addition to existing tools. Especially the tips and hints to migrate from older Ansible versions to current versions and the function to fix found errors are great!"

Sebastian,

System Engineer

"Spotter has allowed me to easily convert an Ansible role and many playbooks to be able to run on the latest Ansible versions. I'm excited to share this tool with my team and my company."

Matt,

Senior Infrastructure Engineer

"Ansible security scanning, assisted playbook writing, and custom policies functionalities of Steampunk Spotter greatly simplify and fast track my Ansible development experience."

Ioannis M.,

Solutions Architect

trusted-by-img trusted-by-img

Trusted and recommended by Red Hat.

Easily upgrade to the latest Ansible version

Check if your playbooks are compatible with a specific Ansible version, identify issues you need to resolve, get advice on how to ease migrations, and upgrade playbooks in minutes instead of hours.

Output without specifying Ansible version

Output with Ansible version specified

upgrades migrations versions

️Prevent downtime and simplify migrations across different versions.

upgrades name changes redirects

Identify name changes and redirects in collections, modules and parameters and default value changes.

upgrades deprecated modules parameters

Detect deprecated modules and their parameters.

upgrades qualified collection names

Check for fully qualified collection names.

  • Prevent downtime and simplify migrations across different versions.
  • Identify name changes and redirects in collections, modules and parameters and default value changes.
  • Detect deprecated modules and their parameters.
  • Check for fully qualified collection names.
spotter secure playbook execution

Achieve secure playbook execution

Add an extra layer of security. Understand what will happen when you run the playbooks and follow security best practices to minimize security risks, downtime, and costs.

spotter secure playbook execution
  • prevent misconfigurations, security vulnerabilities or policy violations
  • proactively evaluate runtime security threats and prevent security breaches
  • ensure compliance with security standards
  • include custom policies to ensure automation meets your specific security requirements

Define your custom rules and policies

Add your own rules and policies to ensure all playbooks meet your specific needs, requirements and use cases.

> spotter policies set Policies
Custom policies successfully set.
 > spotter scan playbook.yml
Scanning...success. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00

Check results:
playbook.yml:7:7: ERROR: [E2300] Name value should start with uppercase letter.
playbook.yml:7:7: ERROR: [E2300] Region should be set to europe (eu-...).
playbook.yml:7:7: ERROR: [E2300::IncorrectValue] ec2_group.rules[0] SSH' (Port:22) should not be public.
playbook.yml:7:7: ERROR: [E2300::IncorrectValue] ec2_group.rules[1] should not open the http port (80).
playbook.yml:23:7: ERROR: [E2300] Instances should not be in default security groups.
playbook.yml:23:7: ERROR: [E2300] Name value should end with a dot.
playbook.yml:23:7: ERROR: [E2300] Volume size should be set to less then 128GB.
playbook.yml:41:7: ERROR: [E2300] Name value should end with a dot.
playbook.yml:47:7: HINT: [H1600] Tasks should always be named using the name parameter.
playbook.yml:52:7: ERROR: [E2300] Access key should be written as a variable.

Scan summary:
Spotter took 2.078 s to scan your input.
It resulted in 9 error(s), 0 warning(s) and 1 hint(s).
Can rewrite 0 file(s) with 0 change(s).
Overall status: ERROR

> spotter clear-policies
Custom policies successfully cleared.
> 
  • ensure you follow organizational or industry-specific regulations, standards, or compliance requirements
  • further specify playbook standards, allowed modules and collections
  • define specific naming conventions and limit required values on specific modules and entities
> spotter policies set Policies
Custom policies successfully set.
 > spotter scan playbook.yml
Scanning...success. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00

Check results:
playbook.yml:7:7: ERROR: [E2300] Name value should start with uppercase letter.
playbook.yml:7:7: ERROR: [E2300] Region should be set to europe (eu-...).
playbook.yml:7:7: ERROR: [E2300::IncorrectValue] ec2_group.rules[0] SSH' (Port:22) should not be public.
playbook.yml:7:7: ERROR: [E2300::IncorrectValue] ec2_group.rules[1] should not open the http port (80).
playbook.yml:23:7: ERROR: [E2300] Instances should not be in default security groups.
playbook.yml:23:7: ERROR: [E2300] Name value should end with a dot.
playbook.yml:23:7: ERROR: [E2300] Volume size should be set to less then 128GB.
playbook.yml:41:7: ERROR: [E2300] Name value should end with a dot.
playbook.yml:47:7: HINT: [H1600] Tasks should always be named using the name parameter.
playbook.yml:52:7: ERROR: [E2300] Access key should be written as a variable.

Scan summary:
Spotter took 2.078 s to scan your input.
It resulted in 9 error(s), 0 warning(s) and 1 hint(s).
Can rewrite 0 file(s) with 0 change(s).
Overall status: ERROR

> spotter clear-policies
Custom policies successfully cleared.
> 

Spotter check types

spotter checks best practice

Best practice checks

Structure your playbooks for readability, collaboration and ease of use.

Press button

Validation checks

Verify that modules, parameters, and parameter values within playbooks are correct and accurate.

spotter checks upgrade

Upgrade checks

Check if playbooks are compatible and supported with the latest versions of Ansible and Ansible Collections.

spotter checks security

Custom checks

Customize rules and policies to meet specific organizational, industry and security requirements.

coming soon

Security checks

Check for security misconfiguration within playbooks and assure compliance with security best practices.

Spotter check types

Save time with convenience features

Fix issues automatically

Rewrite your Ansible content with suggested changes in a flash.

Output before rewrite

Output with rewrite used

 > spotter scan playbook.yml
Scanning...success. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00

Check results:
playbook.yml:5:7: ERROR: [E006] Required parameter instance.host was not set in module servicenow.itsm.change_request. Environment fallback was unsuccessful as variable SN_HOST is not set. If you decide to set the environment variable remember to do it on other configuration systems too. Another way is to set the parameter in task directly. View docs at https://docs.steampunk.si/plugins/servicenow/itsm/2.2.0/module/change_request.html.
playbook.yml:18:7: ERROR: [E601] Value of policy in module ansible.builtin.iptables is set to DROPcy=DROP chain=INPUT which does not match any of the possible choices listed in [ACCEPT, DROP, QUEUE, RETURN].

Scan summary:
Spotter took 2.005 s to scan your input.
It resulted in 2 error(s), 0 warning(s) and 0 hint(s).
Can rewrite 0 file(s) with 0 change(s).
Overall status: ERROR
 > 

Get instant help with module documentation

Suggestions are equipped with direct links to module documentation of a specific version.

Generate missing requirements files

Requirements.yml with all the collections you need for the installation is generated automatically.

> ls
playbook.yml
> spotter scan --rewrite playbook.yml
Scanning...success. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00

Rewritten check results:
playbook.yml:5:7: HINT: [H1900] Required collection community.crypto is missing from requirements.yml or requirements.yml is missing.

Remaining check results:
playbook.yml:5:7: ERROR: [E601] Value of provider in module community.crypto.x509_certificate is set to assertonly which does not match any of the possible choices listed in [acme, entrust, ownca, selfsigned]. View docs at https://docs.steampunk.si/plugins/community/crypto/2.15.1/module/x509_certificate.html.

Scan summary:
Spotter took 1.368 s to scan your input.
It resulted in 1 error(s), 0 warning(s) and 1 hint(s).
Did rewrite 1 file(s) with 1 change(s).
Overall status: ERROR
> ls
playbook.yml  requirements.yml
> 

Gain insights for your scans

Analyze scan data, spot trends, monitor progress, and create custom reports with the intuitive reporting feature. Focus on delivering results and make data-driven decisions.

Spotter works where you work

scan playbooks command line

Scan playbooks from command line

Simply install the steampunk-spotter CLI tool as a Python package.

scan git repo

Scan Git repositories from web

Use Spotter app to check the quality of public Git repositories.

scan playbooks github actions

Scan from CI/CD

Integrate Spotter with GitHub Actions and GitLab to scan content within CI/CD workflows.

scan visual studio code

Scan from your favorite code editor

Analyze and get recommendations for your playbooks directly in Visual Studio Code.

  • Scan playbooks from CLI
  • Scan Git repositories from web
  • Scan in GitHub Actions
  • Scan in GitLab
  • Scan in Visual Studio Code

Who is it for?

Development

As a Playbook Developer, you come across different challenges. Documentation is lacking, there's no clear guidance on what's approved, and it's hard to keep up with what's new and best practices.

Use Spotter to:
verify playbook templates or examples, check Ansible core and Collection versions compatibility, understand the implications of Ansible upgrades.

Quality Assurance

As a Quality Assurance Manager, you often wonder what the playbook will really do, especially when there's no documentation available. Will there be a rollback? Will it break something in production?

Use Spotter to:
understand what will happen when you run the playbook, run QA automations without errors, understand best practices and what-if scenarios for your tests.

Operations

As an Operations Manager, you want to anticipate potential issues, but how to do that if you don't know what will happen in case of errors in the playbooks? Or what will happen to them when a new Ansible version pops up?

Use Spotter to:
identify potential vulnerabilities, receive quality reports and recommendations for improvements, achieve reliable execution of automation.

Security

As IT's infrastructure continues to evolve and become more complex, it's nearly impossible for security specialists to keep it secure at all times without the help of reliable tools.

Use Spotter to:
prevent misconfigurations and security breaches, ensure corporate standards of compliance, achieve secure execution of automation.

AS SEEN ON
brandpush-leafbrandpush-leaf
AND OVER 450 NEWS SITES
check-markVerified by BrandPush.co