Components: disable LoadRestrictions not working with Components

[ptr1120]

What happened?

I executed kustomize kustomize build --load-restrictor=LoadRestrictionsNone ./test/ in order to render my manifest given below.

What did you expect to happen?

Successfully generated kustomize output.

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

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: test

resources:
  # Manifests
  - https://github.com/ptr1120/kustomize-bug.git/deploy/kustomize/manifests?ref=main

components:
  # MongoDb instance only for development
  - https://github.com/ptr1120/kustomize-bug.git/deploy/kustomize/components/mongodb-replicaset?ref=main
  # this is working - ../../../../<redacted>/Desktop/kustomize-bug/deploy/kustomize/components/mongodb-replicaset

Expected output

Successfully generated kustomize output.

Actual output

Error: accumulating components: accumulateDirectory: "recursed accumulation of path '\AppData\Local\Temp\kustomize-761041946\deploy\kustomize\components\mongodb-replicaset': accumulating resources: accumulation err='accumulating resources from './../../manifests/generated/mongodb.yaml': security; file '\AppData\Local\Temp\kustomize-761041946\deploy\kustomize\manifests\generated\mongodb.yaml' is not in or below '\AppData\Local\Temp\kustomize-761041946\deploy\kustomize\components\mongodb-replicaset'': must build at directory: '\AppData\Local\Temp\kustomize-761041946\deploy\kustomize\manifests\generated\mongodb.yaml': file is not directory"

Kustomize version

v5.4.1

Operating system

Windows

[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/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ptr1120]

/remove-lifecycle stale