I totally get the confusion when moving from CircleCI Version 1 to Version 2—especially when features you relied on (like filtering by repository owner) don’t have a direct replacement. Let’s walk through this:

How it worked in CircleCI v1 #

In v1, you could explicitly specify an owner parameter within your deployment config to restrict deployments to a specific repository owner. Here’s the example from the official docs:

deployment:
  master:
    branch: master
    owner: circleci
    commands:
      - ./deploy_master.sh

The v2 Gap #

In CircleCI v2, while you have robust filters to control workflows/jobs based on branches and tags (like the snippet below), there’s no official, built-in equivalent to the v1 owner filter for workflows. After checking official documentation and community resources, this isn’t a native feature in v2’s core configuration syntax.

Here’s how you’d use filters for branches/tags in v2:

workflows:
  deploy-workflow:
    jobs:
      - deploy:
          filters:
            branches:
              only: master
            tags:
              only: /^v\d+\.\d+\.\d+$/

A Manual Workaround #

Even though there’s no direct owner filter, you can replicate the behavior by adding a conditional check in your job steps. CircleCI provides the CIRCLE_PROJECT_USERNAME environment variable, which stores the repository owner’s username. You can use this to validate the owner before running critical steps like deployment:

jobs:
  deploy:
    steps:
      - checkout
      - run:
          name: Validate Repository Owner
          command: |
            if [ "$CIRCLE_PROJECT_USERNAME" != "circleci" ]; then
              echo "This deployment is restricted to the 'circleci' repository owner."
              exit 1
            fi
      - run: ./deploy_master.sh

This ensures the job exits immediately if it’s not running under the expected owner, mimicking the v1 owner filter’s purpose at the job level.

内容的提问来源于stack exchange，提问作者keba