docs: Drafted Software Distribution Hub

[ashokdevtron]

• Created dedicated section (README.md, tenants.md, release-hub.md)
• Created an entry in SUMMARY.md
• Showed tenants as a prerequisite to releasehub-related actions
• Added Enterprise tagging
• Added visuals (snapshots, gifs, videos)
• Explained the purpose in README.md (Why and when and who)
• Gave examples wherever necessary for the user-input fields
• Explained rescind and on-hold actions in Extras
• Showed Partial Release and Full Release in Extras
• Included RBAC (super-admin as of now)

[abhibhaw]

I'm not sure if this is planned in next phase but few missing stuff:

1. How release stages dependency is goverened?
2. Talk about unmapped environment
3. Release notes and catalog of tenant and releases
4. Defining applications at release track (Guessing this will be in next phase of doc)
5. RBAC for deploying with release is not superadmin anymore (Guessing this will be in next phase of doc)
6. Release track Dashboard (Guessing this will be in next phase of doc)

[ashokdevtron]

I'm not sure if this is planned in next phase but few missing stuff:

1. How release stages dependency is goverened?
2. Talk about unmapped environment
3. Release notes and catalog of tenant and releases
4. Defining applications at release track (Guessing this will be in next phase of doc)
5. RBAC for deploying with release is not superadmin anymore (Guessing this will be in next phase of doc)
6. Release track Dashboard (Guessing this will be in next phase of doc)

1. Need to discuss with you
2. Need to discuss with you
3. Added 👍
4. Hmm. Didn't get it.
5. Updated 👍
6. Need to discuss with you

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10220829	Triggered	Generic High Entropy Secret	a8f7860	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	a8f7860	charts/devtron/values.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[abhibhaw]

Suggested minor changes, can be picked up in next version of this doc too

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud