Merge pull request #6867 from zapbot/crowdin-update

Update localized resources

Author: psiinon

addOns/automation/src/main/javahelp/org/zaproxy/addon/automation/resources/help_ar_SA/contents/environment.html

@@ -51,7 +51,7 @@ <H1>Automation Framework - Environment</H1>
             value:                     # The header value
       sessionManagement:
         method:                        # String, one of 'cookie', 'http', 'script'
-        parameters:                    # List of 0 or more parameters - may include any required for scripts
+        parameters:                    # List of parameters - may include any required for scripts
           script:                      # String, path to script, only for 'script' session management
           scriptEngine:                # String, the name of the script engine to use, only for 'script' session management
       technology:
@@ -72,9 +72,10 @@ <H1>Automation Framework - Environment</H1>
             period:                    # Int, the period. Default: 30
             digits:                    # Int, the number of digits. Default: 6
             algorithm:                 # String, the algorithm. Default: SHA1
-  vars:                                # List of 0 or more custom variables to be used throughout the config file
+  vars:                                # List of custom variables to be used throughout the config file
     myVarOne: CustomConfigVarOne       # Can be used as ${myVarOne} anywhere throughout the config
     myVarTwo: ${myVarOne}.VarTwo       # Can refer other vars
+  configs:                             # List of generic config parameters, as per the ZAP "-config" cmd line option
   parameters:
     failOnError: true                  # If set exit on an error
     failOnWarning: false               # If set exit on a warning
@@ -93,7 +94,30 @@ <h3>Variables</h3>
 Variables can be defined in the 'vars' section.
 They can be hardcoded, refer to other variables or refer to system environment variables in the same way as above, e.g. '${envvar}'. 
 In case there are two variables with the same name, the value of the system variable would be preferred. 
-  
+
+<h3>Configs</h3>
+
+The 'configs' section can be used to define any value that can be set in the ZAP configuration file, which works in the same way as the ZAP '-config' command line option.
+<p>
+The advantages of using this section instead of the command line are:
+<ol>
+<li>The configuration will be self contained in the plan
+<li>The ZAP team will monitor the keys used in this way (when telemetry is enabled) and prioritise adding full support for the most frequently used ones
+<li>Warnings will be raised when a key being used has a better solution available
+</ol>
+
+No validation is performed on the keys and values, so you are responsible for checking that your configuration
+is correct. Invalid keys will be silently ignored.
+<p>
+The recommended way to determine the keys is documented in the FAQ:
+<a href="https://www.zaproxy.org/faq/how-do-you-find-out-what-key-to-use-to-set-a-config-value-on-the-command-line/">How do you find out what key to use to set a config value on the command line?</a>
+<p>
+A working example, which sets the number of passive scan threads, is:
+<pre>
+configs:
+  pscans.threads: 8
+</pre> 
+
 <h3>Format Changes</h3>
 
 Originally the 'engine' and 'scriptEngine' fields were directly under the 'sessionManagement' element - this is still supported when reading plans but they

addOns/automation/src/main/javahelp/org/zaproxy/addon/automation/resources/help_az_AZ/contents/environment.html

@@ -51,7 +51,7 @@ <H1>Automation Framework - Environment</H1>
             value:                     # The header value
       sessionManagement:
         method:                        # String, one of 'cookie', 'http', 'script'
-        parameters:                    # List of 0 or more parameters - may include any required for scripts
+        parameters:                    # List of parameters - may include any required for scripts
           script:                      # String, path to script, only for 'script' session management
           scriptEngine:                # String, the name of the script engine to use, only for 'script' session management
       technology:
@@ -72,9 +72,10 @@ <H1>Automation Framework - Environment</H1>
             period:                    # Int, the period. Default: 30
             digits:                    # Int, the number of digits. Default: 6
             algorithm:                 # String, the algorithm. Default: SHA1
-  vars:                                # List of 0 or more custom variables to be used throughout the config file
+  vars:                                # List of custom variables to be used throughout the config file
     myVarOne: CustomConfigVarOne       # Can be used as ${myVarOne} anywhere throughout the config
     myVarTwo: ${myVarOne}.VarTwo       # Can refer other vars
+  configs:                             # List of generic config parameters, as per the ZAP "-config" cmd line option
   parameters:
     failOnError: true                  # If set exit on an error
     failOnWarning: false               # If set exit on a warning
@@ -93,7 +94,30 @@ <h3>Variables</h3>
 Variables can be defined in the 'vars' section.
 They can be hardcoded, refer to other variables or refer to system environment variables in the same way as above, e.g. '${envvar}'. 
 In case there are two variables with the same name, the value of the system variable would be preferred. 
-  
+
+<h3>Configs</h3>
+
+The 'configs' section can be used to define any value that can be set in the ZAP configuration file, which works in the same way as the ZAP '-config' command line option.
+<p>
+The advantages of using this section instead of the command line are:
+<ol>
+<li>The configuration will be self contained in the plan
+<li>The ZAP team will monitor the keys used in this way (when telemetry is enabled) and prioritise adding full support for the most frequently used ones
+<li>Warnings will be raised when a key being used has a better solution available
+</ol>
+
+No validation is performed on the keys and values, so you are responsible for checking that your configuration
+is correct. Invalid keys will be silently ignored.
+<p>
+The recommended way to determine the keys is documented in the FAQ:
+<a href="https://www.zaproxy.org/faq/how-do-you-find-out-what-key-to-use-to-set-a-config-value-on-the-command-line/">How do you find out what key to use to set a config value on the command line?</a>
+<p>
+A working example, which sets the number of passive scan threads, is:
+<pre>
+configs:
+  pscans.threads: 8
+</pre> 
+
 <h3>Format Changes</h3>
 
 Originally the 'engine' and 'scriptEngine' fields were directly under the 'sessionManagement' element - this is still supported when reading plans but they

addOns/automation/src/main/javahelp/org/zaproxy/addon/automation/resources/help_bs_BA/contents/environment.html

@@ -51,7 +51,7 @@ <H1>Automation Framework - Environment</H1>
             value:                     # The header value
       sessionManagement:
         method:                        # String, one of 'cookie', 'http', 'script'
-        parameters:                    # List of 0 or more parameters - may include any required for scripts
+        parameters:                    # List of parameters - may include any required for scripts
           script:                      # String, path to script, only for 'script' session management
           scriptEngine:                # String, the name of the script engine to use, only for 'script' session management
       technology:
@@ -72,9 +72,10 @@ <H1>Automation Framework - Environment</H1>
             period:                    # Int, the period. Default: 30
             digits:                    # Int, the number of digits. Default: 6
             algorithm:                 # String, the algorithm. Default: SHA1
-  vars:                                # List of 0 or more custom variables to be used throughout the config file
+  vars:                                # List of custom variables to be used throughout the config file
     myVarOne: CustomConfigVarOne       # Can be used as ${myVarOne} anywhere throughout the config
     myVarTwo: ${myVarOne}.VarTwo       # Can refer other vars
+  configs:                             # List of generic config parameters, as per the ZAP "-config" cmd line option
   parameters:
     failOnError: true                  # If set exit on an error
     failOnWarning: false               # If set exit on a warning
@@ -93,7 +94,30 @@ <h3>Variables</h3>
 Variables can be defined in the 'vars' section.
 They can be hardcoded, refer to other variables or refer to system environment variables in the same way as above, e.g. '${envvar}'. 
 In case there are two variables with the same name, the value of the system variable would be preferred. 
-  
+
+<h3>Configs</h3>
+
+The 'configs' section can be used to define any value that can be set in the ZAP configuration file, which works in the same way as the ZAP '-config' command line option.
+<p>
+The advantages of using this section instead of the command line are:
+<ol>
+<li>The configuration will be self contained in the plan
+<li>The ZAP team will monitor the keys used in this way (when telemetry is enabled) and prioritise adding full support for the most frequently used ones
+<li>Warnings will be raised when a key being used has a better solution available
+</ol>
+
+No validation is performed on the keys and values, so you are responsible for checking that your configuration
+is correct. Invalid keys will be silently ignored.
+<p>
+The recommended way to determine the keys is documented in the FAQ:
+<a href="https://www.zaproxy.org/faq/how-do-you-find-out-what-key-to-use-to-set-a-config-value-on-the-command-line/">How do you find out what key to use to set a config value on the command line?</a>
+<p>
+A working example, which sets the number of passive scan threads, is:
+<pre>
+configs:
+  pscans.threads: 8
+</pre> 
+
 <h3>Format Changes</h3>
 
 Originally the 'engine' and 'scriptEngine' fields were directly under the 'sessionManagement' element - this is still supported when reading plans but they

addOns/automation/src/main/javahelp/org/zaproxy/addon/automation/resources/help_da_DK/contents/environment.html

@@ -51,7 +51,7 @@ <H1>Automation Framework - Environment</H1>
             value:                     # The header value
       sessionManagement:
         method:                        # String, one of 'cookie', 'http', 'script'
-        parameters:                    # List of 0 or more parameters - may include any required for scripts
+        parameters:                    # List of parameters - may include any required for scripts
           script:                      # String, path to script, only for 'script' session management
           scriptEngine:                # String, the name of the script engine to use, only for 'script' session management
       technology:
@@ -72,9 +72,10 @@ <H1>Automation Framework - Environment</H1>
             period:                    # Int, the period. Default: 30
             digits:                    # Int, the number of digits. Default: 6
             algorithm:                 # String, the algorithm. Default: SHA1
-  vars:                                # List of 0 or more custom variables to be used throughout the config file
+  vars:                                # List of custom variables to be used throughout the config file
     myVarOne: CustomConfigVarOne       # Can be used as ${myVarOne} anywhere throughout the config
     myVarTwo: ${myVarOne}.VarTwo       # Can refer other vars
+  configs:                             # List of generic config parameters, as per the ZAP "-config" cmd line option
   parameters:
     failOnError: true                  # If set exit on an error
     failOnWarning: false               # If set exit on a warning
@@ -93,7 +94,30 @@ <h3>Variables</h3>
 Variables can be defined in the 'vars' section.
 They can be hardcoded, refer to other variables or refer to system environment variables in the same way as above, e.g. '${envvar}'. 
 In case there are two variables with the same name, the value of the system variable would be preferred. 
-  
+
+<h3>Configs</h3>
+
+The 'configs' section can be used to define any value that can be set in the ZAP configuration file, which works in the same way as the ZAP '-config' command line option.
+<p>
+The advantages of using this section instead of the command line are:
+<ol>
+<li>The configuration will be self contained in the plan
+<li>The ZAP team will monitor the keys used in this way (when telemetry is enabled) and prioritise adding full support for the most frequently used ones
+<li>Warnings will be raised when a key being used has a better solution available
+</ol>
+
+No validation is performed on the keys and values, so you are responsible for checking that your configuration
+is correct. Invalid keys will be silently ignored.
+<p>
+The recommended way to determine the keys is documented in the FAQ:
+<a href="https://www.zaproxy.org/faq/how-do-you-find-out-what-key-to-use-to-set-a-config-value-on-the-command-line/">How do you find out what key to use to set a config value on the command line?</a>
+<p>
+A working example, which sets the number of passive scan threads, is:
+<pre>
+configs:
+  pscans.threads: 8
+</pre> 
+
 <h3>Format Changes</h3>
 
 Originally the 'engine' and 'scriptEngine' fields were directly under the 'sessionManagement' element - this is still supported when reading plans but they

addOns/automation/src/main/javahelp/org/zaproxy/addon/automation/resources/help_de_DE/contents/environment.html

@@ -51,7 +51,7 @@ <H1>Automation Framework - Environment</H1>
             value:                     # The header value
       sessionManagement:
         method:                        # String, one of 'cookie', 'http', 'script'
-        parameters:                    # List of 0 or more parameters - may include any required for scripts
+        parameters:                    # List of parameters - may include any required for scripts
           script:                      # String, path to script, only for 'script' session management
           scriptEngine:                # String, the name of the script engine to use, only for 'script' session management
       technology:
@@ -72,9 +72,10 @@ <H1>Automation Framework - Environment</H1>
             period:                    # Int, the period. Default: 30
             digits:                    # Int, the number of digits. Default: 6
             algorithm:                 # String, the algorithm. Default: SHA1
-  vars:                                # List of 0 or more custom variables to be used throughout the config file
+  vars:                                # List of custom variables to be used throughout the config file
     myVarOne: CustomConfigVarOne       # Can be used as ${myVarOne} anywhere throughout the config
     myVarTwo: ${myVarOne}.VarTwo       # Can refer other vars
+  configs:                             # List of generic config parameters, as per the ZAP "-config" cmd line option
   parameters:
     failOnError: true                  # If set exit on an error
     failOnWarning: false               # If set exit on a warning
@@ -93,7 +94,30 @@ <h3>Variables</h3>
 Variables can be defined in the 'vars' section.
 They can be hardcoded, refer to other variables or refer to system environment variables in the same way as above, e.g. '${envvar}'. 
 In case there are two variables with the same name, the value of the system variable would be preferred. 
-  
+
+<h3>Configs</h3>
+
+The 'configs' section can be used to define any value that can be set in the ZAP configuration file, which works in the same way as the ZAP '-config' command line option.
+<p>
+The advantages of using this section instead of the command line are:
+<ol>
+<li>The configuration will be self contained in the plan
+<li>The ZAP team will monitor the keys used in this way (when telemetry is enabled) and prioritise adding full support for the most frequently used ones
+<li>Warnings will be raised when a key being used has a better solution available
+</ol>
+
+No validation is performed on the keys and values, so you are responsible for checking that your configuration
+is correct. Invalid keys will be silently ignored.
+<p>
+The recommended way to determine the keys is documented in the FAQ:
+<a href="https://www.zaproxy.org/faq/how-do-you-find-out-what-key-to-use-to-set-a-config-value-on-the-command-line/">How do you find out what key to use to set a config value on the command line?</a>
+<p>
+A working example, which sets the number of passive scan threads, is:
+<pre>
+configs:
+  pscans.threads: 8
+</pre> 
+
 <h3>Format Changes</h3>
 
 Originally the 'engine' and 'scriptEngine' fields were directly under the 'sessionManagement' element - this is still supported when reading plans but they

addOns/automation/src/main/javahelp/org/zaproxy/addon/automation/resources/help_el_GR/contents/environment.html

@@ -51,7 +51,7 @@ <H1>Automation Framework - Environment</H1>
             value:                     # The header value
       sessionManagement:
         method:                        # String, one of 'cookie', 'http', 'script'
-        parameters:                    # List of 0 or more parameters - may include any required for scripts
+        parameters:                    # List of parameters - may include any required for scripts
           script:                      # String, path to script, only for 'script' session management
           scriptEngine:                # String, the name of the script engine to use, only for 'script' session management
       technology:
@@ -72,9 +72,10 @@ <H1>Automation Framework - Environment</H1>
             period:                    # Int, the period. Default: 30
             digits:                    # Int, the number of digits. Default: 6
             algorithm:                 # String, the algorithm. Default: SHA1
-  vars:                                # List of 0 or more custom variables to be used throughout the config file
+  vars:                                # List of custom variables to be used throughout the config file
     myVarOne: CustomConfigVarOne       # Can be used as ${myVarOne} anywhere throughout the config
     myVarTwo: ${myVarOne}.VarTwo       # Can refer other vars
+  configs:                             # List of generic config parameters, as per the ZAP "-config" cmd line option
   parameters:
     failOnError: true                  # If set exit on an error
     failOnWarning: false               # If set exit on a warning
@@ -93,7 +94,30 @@ <h3>Variables</h3>
 Variables can be defined in the 'vars' section.
 They can be hardcoded, refer to other variables or refer to system environment variables in the same way as above, e.g. '${envvar}'. 
 In case there are two variables with the same name, the value of the system variable would be preferred. 
-  
+
+<h3>Configs</h3>
+
+The 'configs' section can be used to define any value that can be set in the ZAP configuration file, which works in the same way as the ZAP '-config' command line option.
+<p>
+The advantages of using this section instead of the command line are:
+<ol>
+<li>The configuration will be self contained in the plan
+<li>The ZAP team will monitor the keys used in this way (when telemetry is enabled) and prioritise adding full support for the most frequently used ones
+<li>Warnings will be raised when a key being used has a better solution available
+</ol>
+
+No validation is performed on the keys and values, so you are responsible for checking that your configuration
+is correct. Invalid keys will be silently ignored.
+<p>
+The recommended way to determine the keys is documented in the FAQ:
+<a href="https://www.zaproxy.org/faq/how-do-you-find-out-what-key-to-use-to-set-a-config-value-on-the-command-line/">How do you find out what key to use to set a config value on the command line?</a>
+<p>
+A working example, which sets the number of passive scan threads, is:
+<pre>
+configs:
+  pscans.threads: 8
+</pre> 
+
 <h3>Format Changes</h3>
 
 Originally the 'engine' and 'scriptEngine' fields were directly under the 'sessionManagement' element - this is still supported when reading plans but they