What is the replacement for bases?

[tamalsaha]

kustomize/api/types/kustomization.go

Lines 85 to 88 in 2a8a17e

	// Deprecated.
	// Anything that would have been specified here should
	// be specified in the Resources field instead.
	Bases []string `json:"bases,omitempty" yaml:"bases,omitempty"`

I see bases is deprecated. What is the replacement?

[chancez]

If I understand correctly, resources can be used to point to a directory containing a kustomization.yaml for these purposes.

[pwittrock]

@chancez correct -- you can specify bases as resources

[MikaelSmith]

#776 (comment) demonstrates they have some notable differences. Bases seems to be the better option for what I'm trying to do and several other uses I've seen.

Update: I guess this is only an issue in the version of kustomize shipped with kubectl 1.18.

[tolgaingenc]

But if you define bases with resources it requires the base to be "in or below" which is a bad idea if you wont dublicate base per env. How am I supposed to put base within dev or prod?

MyRepo
├───base
│ ├───db
│ ├───frontend
│ ├───service1
│ ├───service2
└───env
│ ├───dev
│ ├───prod

[coderatchet]

Can someone please confirm if this is/will be fixed by 1.19?

[timhughes]

@coderatchet Added an explanation on this ticket (as far as i can work it out) kubernetes/kubectl#891 (comment)