kinflate: remove prune field from the manifest

This commit is contained in:
Sunil Arora 2018-04-04 10:41:59 -07:00
parent d269e5905c
commit f70ce7da75
3 changed files with 0 additions and 15 deletions

View File

@ -110,19 +110,6 @@ type Manifest struct {
// If a secret want to have a base and an overlay, it should go to Bases and
// Overlays fields.
SecretGenerators []SecretGenerator `json:"secretGenerators,omitempty" yaml:"secretGenerators,omitempty"`
// Whether prune resources not defined in Kube-manifest.yaml, similar to
// `kubectl apply --prune` behavior.
Prune bool `json:"prune,omitempty" yaml:"prune,omitempty"`
// TODO: figure out what the behavior details should be.
// Whether PersistentVolumeClaims should be deleted with the other resources.
// OwnPersistentVolumeClaims bool `json:"ownPersistentVolumeClaims,omitempty" yaml:"ownPersistentVolumeClaims,omitempty"`
// TODO: figure out what the behavior details should be.
// Whether recursive look for Kube-manifest.yaml, similar to
// `kubectl --recursive` behavior.
// Recursive bool `json:"recursive,omitempty" yaml:"recursive,omitempty"`
}
// ConfigMap contains the metadata of how to generate a configmap.

View File

@ -48,7 +48,6 @@ resources: []
configmaps: []
# There could be secrets in Base, if just using a fork/rebase workflow
secrets: []
recursive: true
`
type initOptions struct {

View File

@ -33,4 +33,3 @@ secretGenerators:
tls.crt: "cat secret/tls.cert"
tls.key: "cat secret/tls.key"
type: "kubernetes.io/tls"
prune: true # Id make this the default