configMapGenerator unable to replace/merge ConfigMap from another Component

[hylowaker]

What happened?

The configMapGenerator from a Component is not visible to parent configMapGenerator.

Similar issue with #5836

What did you expect to happen?

It generates a merged ConfigMap from two configMapGenerator, one from parent and the other from a Component.

How can we reproduce it (as minimally and precisely as possible)?

# base/kustomization.yaml

components:
- foo/

configMapGenerator:
- behavior: merge
  literals:
  - hello=wolrd
  name: some-config
  namespace: default

# base/foo/kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1alpha1
kind: Component

resources:
- inner/

# base/foo/inner/kustomization.yaml

configMapGenerator:
- name: some-config
  namespace: default
  literals:
  - foo=bar

generatorOptions:
  disableNameSuffixHash: true

Then run kustomize build .

Expected output

apiVersion: v1
data:
  foo: bar
  hello: wolrd
kind: ConfigMap
metadata:
  name: some-config
  namespace: default

Actual output

Error: merging from generator &{0x140003f4680 <nil>}: id resid.ResId{Gvk:resid.Gvk{Group:"", Version:"v1", Kind:"ConfigMap", isClusterScoped:false}, Name:"some-config", Namespace:"default"} does not exist; cannot merge or replace

Kustomize version

v5.6.0

Operating system

MacOS

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.