Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28399

Fix Aspera configuration property names

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: ADDONS_10.10
    • Component/s: Aspera Connector
    • Backlog priority:
      200
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      The following properties were renamed to correct a naming typo:

      1. aspera.acess.key.id
      2. aspera.acess.key.secret
      3. aspera.download.acess.key.id
      4. aspera.download.acess.key.secret

      After this ticket the properties will be:

      1. aspera.access.key.id
      2. aspera.access.key.secret
      3. aspera.download.access.key.id
      4. aspera.download.access.key.secret
      Show
      The following properties were renamed to correct a naming typo: aspera.acess.key.id aspera.acess.key.secret aspera.download.acess.key.id aspera.download.acess.key.secret After this ticket the properties will be: aspera. access .key.id aspera. access .key.secret aspera.download. access .key.id aspera.download. access .key.secret
    • Sprint:
      nxApps 2020 Cycle 7

      Description

      s/acess/access/g

       

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour
                  1h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.