Uploaded image for project: 'Magnolia CLI npm module '
  1. Magnolia CLI npm module
  2. NPMCLI-190

jumpstart can not handle CE artifacts from the "magnolia.public.maintenance.releases" repo

    Details

    • Type: Task
    • Status: Open
    • Priority: Neutral
    • Resolution: Unresolved
    • Affects Version/s: 3.0.1
    • Fix Version/s: None
    • Labels:
      None

      Description

      Summary:
      As a Magnolia customer with EE license which has permissions to read from the magnolia.public.maintenance.releases repository, I want be able to grap and install such an artifact with jumpstart too.


       

       When running this command

      mgnl jumpstart -m 5.4.17

      CLI fails with:
      ERR! Artifact was not found in Nexus. Please check that version you provided is correct.

      The artifact magnolia-community-demo-webapp-5.4.17.war resides in the repo magnolia.public.maintenance.releases.

      I assume: CLI asks for credentials only, if I choose an EE (or cloud) webapp.

      I currently can "trick" CLI if I manually download magnolia-community-demo-webapp-5.4.17.war and move it to my local __mgnl-artifacts-store, that's where my CLI stores downloaded artifacts. (See downloadsFolder, property downloadsFolder).

      In the case of my example, CLI should ask me as the user for credentials, if the requested artifact is available but in a non-public repository.
      If my creds. are still not sufficient, CLI can then claim that I lack permissions.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                cmeier Christoph Meier
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Date of First Response: