Skip to main content

Upload Policies

Upload Policies let administrators reject packages that should not enter a local repository. In the RepoFlow interface and API, these policies are called Upload Restrictions.

At a glance​

  • Available for: local repositories.
  • Fields: package name and package version.
  • Operators: equals, not equals, contains, not contains, starts with, and ends with.
  • Logic: combine up to six conditions with AND or OR in the visual builder.
  • Access: repository users can view restrictions; workspace and system administrators can create or change them.

RepoFlow also validates that an uploaded artifact can be processed as its repository’s package type. Upload restrictions add your organization’s naming and version policy on top of that package validation.

Create an upload restriction​

  1. Open a local repository and select Upload Restrictions from its details.
  2. Select Add Restriction and give the rule a clear name.
  3. Choose Package Name or Package Version, an operator, and a value.
  4. Add AND or OR conditions when one comparison is not enough.
  5. Save the restriction, then test both an allowed and a blocked upload with your normal package client.

An enabled rule blocks an upload when its expression matches. Multiple enabled upload restrictions are evaluated independently, so a match in any restriction is enough to block the package.

Expression reference​

Each condition has the form Field Operator "Value". Conditions joined with AND form one group; OR separates alternative groups.

(Package Name Starts With "internal-")

Values are case-sensitive. Use the visual builder for routine changes so RepoFlow produces the expression for you.

API​

Use the API to create, update, or delete an upload restriction.