postsubmits:
  kubernetes-sigs/security-profiles-operator:
    - name: post-security-profiles-operator-push-image
      cluster: k8s-infra-prow-build-trusted
      decorate: true
      always_run: true
      branches:
        - ^master$
      spec:
        serviceAccountName: gcb-builder
        containers:
          - image: gcr.io/k8s-testimages/image-builder:v20200901-ab141a0
            command:
              - /run.sh
            args:
              - --project=k8s-staging-security-profiles-operator
              - --scratch-bucket=gs://k8s-staging-security-profiles-operator-gcb
              - .
            env:
              - name: LOG_TO_STDOUT
                value: "y"

postsubmits:
  kubernetes-sigs/security-profiles-operator:
    - name: post-security-profiles-operator-push-image
      cluster: k8s-infra-prow-build-trusted
      decorate: true
      always_run: true
      branches:
        - ^master$
      spec:
        serviceAccountName: gcb-builder
        containers:
          - image: gcr.io/k8s-testimages/image-builder:v20200901-ab141a0
            command:
              - /run.sh
            args:
              - --project=k8s-staging-sp-operator
              - --scratch-bucket=gs://k8s-staging-sp-operator-gcb
              - .
            env:
              - name: LOG_TO_STDOUT
                value: "y"

Fix security-profiles-operator image pushing bucket
Fix security-profiles-operator image pushing bucket

We changed the bucket name to shorthand `security-profile` to `sp` to
fix the name length limitation. This is now reflected here, too.

Signed-off-by: Sascha Grunert <70ab469ddb2ac3e35f32ed7c2fd1cca514b2e879@suse.com>
