Description

As a user, I should be able to update the application's git information like url/revision/docker file path,  in edit import flow and expect those changes should be automatically reflected in the associated pipeline as well.

Acceptance Criteria

1. When an application has a pipeline associated with it then while editing the git information of that application, we must update the following parameters in the associated pipeline.

   GIT_REPO, GIT_REVISION, PATH_CONTEXT, DOCKERFILE

2. Show the Pipeline section
   • disabled & checked checkbox if there is already a Pipeline
   • enabled & unchecked checkbox if there is no Pipeline already associated – checking just goes through the flow we have today
     • Make sure the Build Config adv option is not visible
3. If they change the builder image (and we have a Pipeline for that image) we need to replace the existing `pipeline.spec` with the new template's `pipeline.spec` - just do a 1:1 swap
   • Also make sure we update the `pipeline.dev/runtime` label to the new builder image name
   • Show a warning to the user in the Pipeline section (UX TBD)
4. If the builder image does not have a Pipeline template, we will just remove the `app.kubernetes.io/instance` label off the Pipeline
   • Show a warning to the user in the Pipeline section (UX TBD)
5. Naturally, when the form submits, if a Pipeline is still associated, create a new Pipeline Run

Additional Details:

Initial conversation - https://github.com/openshift/console/pull/6874#issuecomment-710009475