kustomize create --resources does not support remote file references

[scodeman]

Description

kustomisation.yaml file accepts url within resources but the kustomize cli does not allow to create the corresponding file

kustomize create --stack-trace --resources=https://github.com/operator-framework/operator-lifecyclemanager/releases/download/v0.22.0/olm.yaml

Expected output

kustomization.yaml

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
  - https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.22.0/olm.yaml

Actual output

2022/10/25 15:31:43 https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.22.0/olm.yaml has no match

Kustomize version

kustomize/v4.1.3

Platform

macOS amd64

Additional context

Could be that the kustomize cli assumes local files or does not follow redirection on fetching url

[KnVerey]

It seems to me that kustomize create does accept remote URLs, but only for bases, not for individual files. We first try to use the string as an expression referring to local files, and if that fails, we try to treat it as a remote base. If that fails, for some reason we're outputting a message about the first pattern-matching attempt but proceeding without an error (it would also be good to improve this). kustomize build on the other hand does not accept patterns, and first tries to load the string as a raw resources file, then as a base. Agreed that create's resources flag ideally would support all the formats that build's resources field supports (NB not the other way around though, as build is more restrictive by design).

/retitle kustomize create --resources does not support remote file references
/triage accepted

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten