Enable existing app for GitOps workflow

[sspeiche]

Description

As a developer, I want to have a simple command to "GitOps-enable" my existing application so I
can easily have CI enabled.

This command could look something like: odo gitops-enable --stak=springboot .
which could read some information from the associated stak or auto-detect.

Acceptance Criteria

• User is able to execute command and have supporting files generated for an existing application
• User is able to specify that files are to be added to existing app directory structure or staged in a new repo
• User should be able to easily apply these files to validate the desired behavior of their app with gitops flow.

Note

• There is a related epic to "pipeline enable" Integration with pipelines (CI) #1238

[sbose78]

I'll update this to have the details of the 'gitops day 2 Add Application' flow.

[girishramnani]

@sbose78 If you could please share maybe just a break down whats done and whats left so I can plan for this issue/milestone.

[fgiloux]

+1. This would be very useful.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[girishramnani]

seems like the kam project took over the enablement of GitOps Pipeline
link - https://github.com/redhat-developer/kam

[girishramnani]

so should we close this epic @sspeiche @serenamarie125 ?

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.