Metadata-Version: 2.1
Name: insight-plugin
Version: 0.4.2
Summary: Plugin tooling for the Rapid7 Insight platform
Home-page: https://github.com/rapid7/insight-plugin
Author: Rapid7 Integrations Alliance
Author-email: integrationalliance@rapid7.com
License: MIT
Platform: UNKNOWN
Classifier: Programming Language :: Python :: 3
Classifier: Operating System :: OS Independent
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Topic :: Software Development :: Build Tools
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: jinja2 (==3.1.2)
Requires-Dist: pyyaml (==5.4.1)
Requires-Dist: jsonschema (==2.3.0)
Requires-Dist: mdutils (==1.3.1)
Requires-Dist: jq (==1.4.0)
Requires-Dist: insightconnect-integrations-validators (~=2.0)
Requires-Dist: markupsafe (==2.0.1)
Requires-Dist: ruamel.yaml (==0.17.21)
Requires-Dist: ruamel.yaml.clib (==0.2.7)
Requires-Dist: semver (==2.13.0)
Requires-Dist: parameterized (==0.8.1)

# Insight Plugin - CLI Tooling for plugin development

## Commands

### Create
Create a new plugin.

This command will generate the skeleton folder structure and 
code for a new plugin, based on the provided plugin.spec.yaml file.

### Export
Export a plugin Docker image to a tarball.

This tarball can be uploaded as a custom plugin 
via the import functionality in the InsightConnect UI.

### Refresh
Refresh the plugin.

This command will update the current plugin code, 
when updates are made in the plugin.spec.yaml file

### Validate
Validate / Run checks against the plugin. 

This command performs quality control checks on the current 
state of the plugin. 
This should be run before finalizing any new updates.

### Semver
Update the plugin versioning. 

This command should be run after finalizing any updates, 
defect fixes or new functionality, to update the versioning

### Samples
Create test samples for actions and triggers. 

This command will create new files under the 'tests' folder which can be 
used to test each new action/trigger. 
Note if a file already exists for a particular action/trigger, it will be overwritten.

### Run
Run an action/trigger from a json test file (created during sample generation)

### Server
Run the plugin in HTTP mode. 

This allows an external API testing program to be used to test a plugin 

### Shell
Run the plugin via the docker shell to enable advanced debugging


