I want to use the "ecr-login" credHelper for both from and to, but I need to use different environment variables (AWS_PROFILE in my case), because the IAM is different in each case. If it is possible somehow, I would like to know, and if not, I would like to request this feature (just like e.g. environment can be set for dockerClient).

As a workaround, I will now try to run the credHe

We need to add more integration tests (living in the src/it folder) to cover various usage scenarios.

Right now we only have a single test that just checks that the plugin can run a basic test with no additional configuration (This can be used as an example on how to configure other integration tests). We should be testing various configuration options as well.

Requirements:

• The .jmx files

Add 'since' information to plugin configuration parameters by inspecting the commit history.

Currently, the headless scanner extension expects an XML based configuration file and this works ok. But, making the XML is cumbersome and also requires that most of the request URLs be wrapped in CDATA blocks.

IMHO, this would be much simpler, cleaner and much more concise in JSON than in XML, Also, the configuration files for Burp itself seem to be JSON based. So, this move will make it sor