Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-27332

Virtual repo member order not respected in YAML config

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 7.39.0
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
      None

      Description

      When defining virtual repo members in YAML config, the order they are listed in YAML is not respected. Instead they look to be randomly aggregated and applied to a virtual repo, thus causing artifact resolution issues if the order provided matters.

      We enforce configuration via YAML and the order of repositories within a virtual repo are random every time it is applied. I would expect order to be preserved in the way it is defined in YAML.

      For example, an npm virtual repo config:

      virtualRepositories:
        npm-virtual:
          type: npm
          repositories:
            - npm-local
            - npmjs-npm
            - npme-npm
            - openupm-npm
      

      When this is applied though, the order is always random as shown below.

      Can order be preserved when supplied via YAML config?

        Attachments

          Activity

              People

              Assignee:
              Unassigned
              Reporter:
              zpeschke Zachary Peschke
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated: