Skip to content

cf diff and push idempotent #1895

@Perdjesk

Description

@Perdjesk

cf diff similar to kubectl diff
see: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#diff

cf push is not idempotent friendly. Pushing two time the same manifest will results in two different re-stage/restart for the second push which is unnecessary since nothing change.
cf push must not re-stage/restart if nothing change.

What's the user value of this feature request?
Increase automation use cases.
GitOps based workflows re-conciliating the state of CF based on manifests and CF cli.

Who is the functionality for?
Developers

How often will this functionality be used by the user?
()

Who else is affected by the change?
()

Is your feature request related to a problem? Please describe.
See description of feature and unnecessary restart of applications when applying manifest that are not changing anything.

Describe the solution you'd like
See description above.

Describe alternatives you've considered
Comparing manifest locally using YAML diff like tool between the content from Git and cf create-app-manifest

Additional context
()
https://github.com/cloudfoundry/cli/issues/1710 https://github.com/cloudfoundry/cli/issues/1710#issuecomment-508170692 (requesting for symmetric push with pruning)

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions