Profile and require item conflict

[sw360cab]

This file skaffold.yaml is called with

skaffold run -p eks-operators

apiVersion: skaffold/v4beta11
kind: Config
metadata:
  name: gocluster
requires:
  # One of many requires
  - path: ../../cluster/skaffold/traefik-skaffold.yaml
    activeProfiles: &kubeBaseProfiles
    - name: dev
      activatedBy: [net-dev]

profiles:
  - name: net-dev
    activation:
      - kubeContext: kind-live
        env: "INFRA=net"
  - name: eks-operators
    manifests:
      kustomize:
        paths:
          - ../../aws-eks/storage

deploy:
  kubectl: {}

Output is

No tags generated
Starting test...
Starting deploy...
nothing to deploy

But if I save in another file, operators-skaffold.yaml
and launch skaffold run -p eks-operators -f operators-skaffold.yaml

apiVersion: skaffold/v4beta11
kind: Config
metadata:
  name: operators-setup
profiles:
  - name: eks-operators
    manifests:
      kustomize:
        paths:
          ## AWS Storage Class + EKS Storage
          - ../../aws-eks/storage

deploy:
  kubectl: {}

It deploys as expected.

In both cases skaffold render outputs expected yaml.
What is the issue I am having?

[sw360cab]

More weird....

This also works and deploy resources

  # Operators
  - path: ./cluster/skaffold/operators-skaffold.yaml
    activeProfiles:
    - name: eks-operators
      activatedBy: [eks-operators]

Full skaffold.yaml

apiVersion: skaffold/v4beta11
kind: Config
metadata:
  name: gocluster
requires:
  - path: ./cluster/skaffold/operators-skaffold.yaml
    activeProfiles:
    - name: eks-operators
      activatedBy: [eks-operators]

  - path: ../../cluster/skaffold/traefik-skaffold.yaml
    activeProfiles: &kubeBaseProfiles
    - name: dev
      activatedBy: [net-dev]

profiles:
  - name: net-dev
    activation:
      - kubeContext: kind-live
        env: "INFRA=net"
  - name: eks-operators

deploy:
  kubectl: {}

[mattsanta]

To help debug you could try resolving the Skaffold file to see what it looks like once profiles are activated:

skaffold diagnose -f {filename} -p {profile}

[sw360cab]

I can confirm that also diagnose with the original file shows the correct information

No tags generated
Skaffold version: 95fb592deb61a4e290edca4925bd7c9c2fa93f6c
Configuration version: skaffold/v4beta13
Number of artifacts: 0

Configuration
Skaffold version: 95fb592deb61a4e290edca4925bd7c9c2fa93f6c
Configuration version: skaffold/v4beta13
Number of artifacts: 0

Configuration
Skaffold version: 95fb592deb61a4e290edca4925bd7c9c2fa93f6c
Configuration version: skaffold/v4beta13
Number of artifacts: 0

Configuration
Skaffold version: 95fb592deb61a4e290edca4925bd7c9c2fa93f6c
Configuration version: skaffold/v4beta13
Number of artifacts: 0

Configuration
Skaffold version: 95fb592deb61a4e290edca4925bd7c9c2fa93f6c
Configuration version: skaffold/v4beta13
Number of artifacts: 0

Configuration
apiVersion: skaffold/v4beta13
kind: Config
metadata:
  name: traefik-setup
build:
  tagPolicy:
    gitCommit: {}
  local: {}
deploy:
  kubectl: {}
  logs:
    prefix: container
---
apiVersion: skaffold/v4beta13
kind: Config
metadata:
  name: gocluster
build:
  tagPolicy:
    gitCommit: {}
  local: {}
manifests:
  kustomize:
    paths:
      - <Project_folder>/aws-eks/storage
deploy:
  kubectl: {}
  logs:
    prefix: container

but the output is still

No tags generated
Starting test...
Starting deploy...
nothing to deploy