Persist environment parameters during deployment

[alexmt]

Each environment has parameters which are used to generate resources manifests. It would be useful to persist and display parameters which were used to deploy the application.

• Persist parameters during deployment
• Render parameters on application details page

[merenbach]

@alexmt Where could I go to start understanding how to do the first subtask? What would this "persisting" consist of—just making available to the UI through an API?

[alexmt]

@merenbach, right now we only need to show parameters to user. I would propose to store in Application CRD in AppStatus.RecentDeployment field:

// ApplicationStatus contains information about application status in target environment.
type ApplicationStatus struct {
	ComparisonResult ComparisonResult `json:"comparisonResult" protobuf:"bytes,1,opt,name=comparisonResult"`
// new field:
        RecentDeployment DeploymentInfo `json:"deploymentInfo" protobuf:"bytes,2,opt,name=deploymentInfo"`
}

RecentDeployment should be set in https://github.com/argoproj/argo-cd/blob/master/server/application/application.go#L117.

Parameters can be retrieved using ks param list --env <envNameHere>

[merenbach]

This is being worked on in the https://github.com/merenbach/argo-cd/tree/recent-deployments branch. Ksonnet data retrieval is implemented, and the RPC retrieval should be there (untested so far). To finish fleshing out, need to determine proper data structure for storing DeploymentInfo.