search

nembery / vistoq2

THIS REPO HAS MOVED TO palo alto networks organization
0 stars 1 forks source link

Support hidden default variables along with form-based per-deployment variables #2

Open scotchoaf opened 5 years ago

scotchoaf commented 5 years ago

The templates support 2 types of variables: MSSP specific and customer specific.

The MSSP specific are used globally/regionally by the MSSP for their entire set of deployments. These are not exposed per device deployment in the web forms. Usage would be a conf file or hidden form fields when standing up the service as an MSSP.

The customer specific variables would be exposed in the form fields for each unique deployment. These would be autogenerated, pulled from OSS systems, or entered manually per customer.

Goal is to support both template types without a complete list of variables in each web form input.

nembery commented 5 years ago

would be interesting to support a 'variable.override' file in each snippet dir that way we can add local overrides and use the vistoq2 view logic to only show fields that do not appear in the override files. This would also support CI/CD type testing. I.E. clone a repo, write out overrides into this file and run some tests / deployments / etc.

Propose we open an issue in panhandler repo for a local .override file that acts as a means to supply local variables

scotchoaf commented 5 years ago

Also see a similar issue with 'extends' and the parent snippets containing variables. For example, gold extends from skillet, but only the gold variables are captured in the submitted form so the load fails.

Or perhaps another issue. Would assume the defaults are captured if no form entry provided.