Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-4220

CLONE - Typo in CLI for the read-resource-description for the deployment scanner subsystem

    XMLWordPrintable

Details

    • Hide

      [standalone@localhost:9999 scanner=default] :read-resource-description
      {
      "outcome" => "success",
      "result" => {
      "description" => "The configuration of the deployment scanner subsystem",
      "attributes" => {
      "relative-to" =>

      { "type" => STRING, "description" => "Reference to a filesystem path defined in the \"paths\" section of the server configuration.", "expressions-allowed" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      ,
      "path" =>

      { "type" => STRING, "description" => "The actual filesystem path to be scanned. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path.", "expressions-allowed" => true, "nillable" => false, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      ,
      "auto-deploy-exploded" =>

      { "type" => BOOLEAN, "description" => "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content.", "expressions-allowed" => true, "nillable" => true, "default" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      ,
      "auto-deploy-xml" =>

      { "type" => BOOLEAN, "description" => "Controls whether XML deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file.", "expressions-allowed" => true, "nillable" => true, "default" => true, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      ,
      "scan-enabled" =>

      { "type" => BOOLEAN, "description" => "Flag indicating that all scanning (including initial scanning at startup) should be disabled.", "expressions-allowed" => true, "nillable" => true, "default" => true, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      ,
      "scan-interval" =>

      { "type" => INT, "description" => "Periodic interval, in milliseconds, at which the repository should be scanned for changes. A value of less than 1 indicates the repository should only be scanned at initial startup.", "expressions-allowed" => true, "nillable" => true, "default" => 5000, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      ,
      "auto-deploy-zipped" =>

      { "type" => BOOLEAN, "description" => "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file.", "expressions-allowed" => true, "nillable" => true, "default" => true, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      ,
      "deployment-timeout" =>

      { "type" => LONG, "description" => "Timeout, in seconds, a deployment is allows to execute before being canceled. The default is 60 seconds.", "expressions-allowed" => true, "nillable" => true, "default" => 60, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }

      },
      "operations" => undefined,
      "children" => {}
      }
      }

      Show
      [standalone@localhost:9999 scanner=default] :read-resource-description { "outcome" => "success", "result" => { "description" => "The configuration of the deployment scanner subsystem", "attributes" => { "relative-to" => { "type" => STRING, "description" => "Reference to a filesystem path defined in the \"paths\" section of the server configuration.", "expressions-allowed" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } , "path" => { "type" => STRING, "description" => "The actual filesystem path to be scanned. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path.", "expressions-allowed" => true, "nillable" => false, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } , "auto-deploy-exploded" => { "type" => BOOLEAN, "description" => "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content.", "expressions-allowed" => true, "nillable" => true, "default" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } , "auto-deploy-xml" => { "type" => BOOLEAN, "description" => "Controls whether XML deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file.", "expressions-allowed" => true, "nillable" => true, "default" => true, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } , "scan-enabled" => { "type" => BOOLEAN, "description" => "Flag indicating that all scanning (including initial scanning at startup) should be disabled.", "expressions-allowed" => true, "nillable" => true, "default" => true, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } , "scan-interval" => { "type" => INT, "description" => "Periodic interval, in milliseconds, at which the repository should be scanned for changes. A value of less than 1 indicates the repository should only be scanned at initial startup.", "expressions-allowed" => true, "nillable" => true, "default" => 5000, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } , "auto-deploy-zipped" => { "type" => BOOLEAN, "description" => "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file.", "expressions-allowed" => true, "nillable" => true, "default" => true, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } , "deployment-timeout" => { "type" => LONG, "description" => "Timeout, in seconds, a deployment is allows to execute before being canceled. The default is 60 seconds.", "expressions-allowed" => true, "nillable" => true, "default" => 60, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } }, "operations" => undefined, "children" => {} } }

    Description

      Potential typo in a description for the auto-deploy-exploded attribute of the deployment scanner. Says "zipped" where it should say "exploded". I suspect the cause is just copying and pasting the auto-deploy-zipped text but missing the "exploded" change.

      I've actually rewritten most of these descriptions in my documentation of the attributes for a reference topic. If you want to check those as potential updates, I can paste them in. I do imply assumed knowledge of boolean values to keep the sentences short.

      For example, I rewrote the auto-deployed-exploded as:

      "Allows the automatic deployment of exploded content without requiring a .dodeploy marker file. Recommended for only basic development scenarios to prevent exploded application deployment from occuring during changes by the developer or operating system."

      Was:

      "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content."

      Attachments

        Activity

          People

            olubyans@redhat.com Alexey Loubyansky
            daveryan_jira Dave Ryan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: