Add dev tooling helper script to populate application lifecycle

[karthikjeeyar]

Fixes

https://issues.redhat.com/browse/HAC-2494

Description

Helper script will create all the custom resources need for the application lifecycle and expects the user to start the build pipeline by merging the PR.

List of resources created:

1. Application
2. Component
3. Integration Tests (both in application and component context)
4. Static environment
5. Managed environment (ReleasePlan is created)

Note: Since appstudio staging user doesn't have enough permissions to create other resources in managed workspace (different ns) , some parts of the code is commented out. If a user has enough permission, then uncommenting the managed workspace resource creation will create entire release setup.

Type of change

• Other (please describe):

Helper script to create a development/testing environment.

Screen shots / Gifs for design review

workflow-graph.mov

How to test or reproduce?

Added Readme:

Description

This script helps to setup a development environment for an entire application lifecycle.

Prerequisites

1. Install the appstudio-staging-ci Github app in your github
2. Copy the content from template.env file and create a new .env file and add your values.

Setup

1. Run the setup script from your root directory and pass your github repository to build.

   helpers/setup.sh https://github.com/your_username_/Project-Name.git

2. Once the setup is complete, merge your new PR in your repository to trigger a new build pipeline.

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

cc: @christianvogt

[codecov]

Codecov Report

Merging #278 (7784af1) into main (1966729) will increase coverage by 0.03%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #278      +/-   ##
==========================================
+ Coverage   73.61%   73.65%   +0.03%     
==========================================
  Files         433      435       +2     
  Lines        9123     9182      +59     
  Branches     2438     2455      +17     
==========================================
+ Hits         6716     6763      +47     
- Misses       2269     2281      +12     
  Partials      138      138              

Impacted Files	Coverage Δ
...nts/IntegrationTest/IntegrationTestDetailsView.tsx	82.35% <0.00%> (ø)
...ipelineRunDetailsView/PipelineRunVisualization.tsx	100.00% <0.00%> (ø)
...elineRunDetailsView/tabs/PipelineRunDetailsTab.tsx	100.00% <0.00%> (ø)
...s/overview/visualization/hooks/useAppBuildNodes.ts	100.00% <0.00%> (ø)
...overview/visualization/hooks/useAppWorkflowData.ts	100.00% <0.00%> (ø)
...rview/visualization/hooks/useAppComponentsNodes.ts	100.00% <0.00%> (ø)
...w/visualization/hooks/useAppApplictionTestNodes.ts	100.00% <0.00%> (ø)
...isualization/hooks/useAppStaticEnvironmentNodes.ts	100.00% <0.00%> (ø)
.../components/topology/factories/GraphErrorState.tsx	88.00% <0.00%> (ø)
src/pages/RedirectPage.tsx	0.00% <0.00%> (ø)
... and 6 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1966729...7784af1. Read the comment docs.

[rottencandy]

Tested the scripts, working fine. Just had a question

[openshift-ci]

@karthikjeeyar: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[rottencandy]

/lgtm

[christianvogt]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, karthikjeeyar, rottencandy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [christianvogt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment