Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    [ProGet] Feature Request/Inquiry: Create 'Package Policies' through PGUtil / API

    Scheduled Pinned Locked Moved Support
    3 Posts 2 Posters 8 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N Offline
      Nils Nilsson
      last edited by

      Hi!

      I'm working on automating the setup of new "workspaces" in ProGet whenever my organization onboards a new product/project.

      I've been reading the documentation for a way to create a new Package Policy without the use of Web GUI actions, but turned up empty handed.

      Is there a already way that I haven't found? If not, is that something you'd be willing to add to your backlog to implement?

      If it is something you would consider implementing, my request is that you can set the Risk Profile during creation, in addition to the three fields available when creating in the Web Gui.

      Example:

      pgutil security policy create \
      --Name="New Policy" \
      --Priority=<'Default' | 'Before Global' | 'After Feed'> \
      --Feeds="nuget-feed, maven-feed, npm-feed" \
      --RiskProfile='{ \
          "Exposure" : "<External | Internal>", \
          "Interface": "<Web Browser | Unspecified>", \
          "Outage"   : "<Unacceptable | Disruptive | Tolerable>", \
          "Breach"   : "<Unacceptable | Disruptive | Tolerable>", \
          "Tampering": "<Unacceptable | Disruptive | Tolerable>" \
      }'
      

      Best regards,
      Nils Nilsson

      dean-houstonD 1 Reply Last reply Reply Quote 0
      • dean-houstonD Offline
        dean-houston inedo-engineer @Nils Nilsson
        last edited by

        Hi @Nils-Nilsson ,

        Thanks for the feature request; this is not currently on our roadmap.

        As you might imagine, it would be a substantial undertaking to develop commands/endpoints for policy management and maintain those through new versions. Given how these will hardly change on an instance of ProGet (most users will have a handful of policies at most), we don't feel the costs bring enough benefit to users.

        It's also worth noting -- SCA/Policies are still relatively new in ProGet (and the industry as a whole), so there are a lot of opportunities to improve them. We'd rather invest in that then making them API-editable (which, would make the more complex to change later as well).

        Note that it's possible to do through the Policies_* endpoints and stored procedures should you really need to.

        -- Dean

        N 1 Reply Last reply Reply Quote 1
        • N Offline
          Nils Nilsson @dean-houston
          last edited by

          Hi @dean-houston .

          Thank you for your response, it makes sense that you wouldn't prioritize this, as I assume my organization is quite an outlier where we need to have one policy for every application that utilizes ProGet.

          Best Regards
          Nils Nilsson

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation