add the ability to specify the profile to run as a paramater

[aaronlippold]

As a user I would like to setup an ongoing set of tasks to run various inspec profiles to targets.

[martezr]

@aaronlippold The profile(s) run by the lambda function can now be specified during invocation of the lambda function but currently requires that the environment variable for the lambda function be left empty. This approach was taken to avoid immediately breaking the existing functionality. I'm leaning towards removing the environment variables altogether but I do like the idea of being able to specify a default value.

[aaronlippold]

Agreed. The biggest value ad for this capability is the ability for us to schedule a set of specific profile runs against to set of nodes. This will require us to parameterize quite a bit I'm not sure if the approach of environment variables are key value pairs or some other type of interface will make the most sense.

…

On Fri, Jan 10, 2020, 11:26 PM Martez Reed ***@***.***> wrote: @aaronlippold <https://github.com/aaronlippold> The profile(s) run by the lambda function can now be specified during invocation of the lambda function but currently requires that the environment variable for the lambda function be left empty. This approach was taken to avoid immediately breaking the existing functionality. I'm leaning towards removing the environment variables altogether but I do like the idea of being able to specify a default value. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALK42BFPUYWW3W3QQB6UYDQ5FC63ANCNFSM4J23BSLA> .