Package: mc-nag
Multi-Cloud (MC) Nag Static Analysis ToolBackgroundmc_nag provides the framework for platform-specific "nag" tools (e.g.azure-nag) to validate IAC templates for patterns that may defy best practices or indicate insecure resources.  It provides base classes for parsers, template data models, and rules so those platform-specific "nag" tools can focus on the platform's logic.Prerequisitespyenv >= 1.2.18Python >=3.7 (from pyenv)Installationpip install mc-nagUsageOnce you've imported modules frommc-nag, you can subclass those base classes to provde a starting point for your platform-specific tool.frommc_nag.base_utils.models.templateimportBaseTemplateclassPlatformTemplate(BaseTemplate):...DevelopmentVS Code Remote DevelopmentThere is a complete remote development environment created and setup with all the tools and settings pre-configured for ease in rule development and creation. You can enable this by using the VS Code Remote development functionality.Install the VS CodeRemote Development extension packOpen the repo in VS CodeWhen prompted "Folder contains a dev container configuration file. Reopen folder to develop in a container" click the "Reopen in Container" buttonWhen opening in the future use the "[Dev Container] mc_nag Development" optionIn the terminal, activate the Python virtual environment withpyenv activate mc-nag-venv(Optional) Create a local.env to set an custom pytest or linting environment variables for the MakefilRule CreationRules are at the crux of mc-nag's purpose.  They create its functionality but are flexible enough to be able to create/update/delete them at will.  Rules are stored within each platform-specific "nag" tool (e.g.azure-nag), however the structure of theBaseRuleclass is defined here.StructureAll rules must be subclassed from theBaseRuleclass.  It contains the basic necessities and structure for a rule class, as well as validation mechanisms to ensure your rule class will behave as expected.Rules accept parameters from the CLI when passed in using the--rule-paramoption to a platform-specific tool such asazure-nag.  Parameters are passed into theBaseRule __init__()method and made available as class attributes for use in any class method includingevaluate().  You can also set default values for attributes in your rule class and override them with the--rule-paramoption (seean example here).Every rule must have at least:Attributesrule_id: Unique identifier for the rule.description: Plain language description of what the rule is trying to accomplish.severity: The impact the rule has on the run of mc-nag.  One of [rule.ERROR,rule.WARNING,rule.STYLE].url: Page at which more information can be found on the rule.resolution: Steps to take in order to remediate any violations the rule finds.category_tags: (optional) Categories are based on specific area of concern.(e.g. "storage", "security", "networking")source_tags: (optional) Source tags specify the origin of the rule creator. (e.g. "company_name", "team_name", "creator_name")Methodsevaluate: Logic to perform the rule's stated function.  Must return a list of violating resources.clean_category_tags: Returns a list of santized category tags from a Rule instance.clean_source_tags: Gives a list of santized tags.Sample rulewhich shows basic structureTestingIt is good practice to create unit tests and multiple example templates to accompany your new rule in order to prove your rule logic works properly.  Tests should consider both good and bad scenarios, as well as any novel scenarios which may crop up in practice.When you have a rule ready for evaluation, you can either pass its containing directory as a--custom-platform-rules-dirCLI option to the platform-specific "nag" executable or, if you have the source checked out, you can place the rule into the platform-specific tool's rules directory.Sample unit testsSample test templatesTemplate Model CreationThe template model is a generic way to represent different platforms' templates.  After a template is parsed, its parsed data is stored in the template model for evaluation by the rule set.StructureAll template models must be subclassed from theBaseTemplateclass.  It contains the basic necessities and structure for a template model class, as well as validation mechanisms to ensure your template model class will behave as expected.Every template model must have at least:Attributestemplate_string: Raw string read from the template file.parsed_template: Platform-specific parser object (e.g.AzureParser), which returns the parsed template model.resources: List of platform-specific resource objects (e.g.AzureResource) created from the parsed template model.parameters: List of platform-specific parameter objects (e.g.AzureParameter) created from the parsed template model.outputs: List of platform-specific output objects (e.g.AzureOutput) created from the parsed template model.functions: List of platform-specific function objects (e.g.AzureFunction) created from the parsed template model.variables: List of platform-specific variable objects (e.g.AzureVariable) created from the parsed template model.The attributes listed above must be defined, even if they are just empty lists.Sample template modelwhich shows basic structureTestingIt is good practice to create unit tests and multiple example templates to accompany your new template model in order to prove your data model logic works properly.  Tests should consider both good and bad scenarios, as well as any novel scenarios which may crop up in practice.Sample unit testsSample test templatesReleasesNote: Before releasing, ensure the version string inmc_nag/__init__.pyhas been updated with the new string.Currently, new releases are generated when a user manually publishes the previously created draft release in the GitHub UI.  Themc-nag workflowwill generate a draft release for the repo via therelease-drafterGitHub Action which contains the list of all changes since the previous release.SupportTo report a bug or request a feature, submit an issue through the GitHub repository viahttps://github.com/stelligent/mc-nag/issues/new.