Github Integrations

[Salman2301]

Description 📣

This PR is focus on updating the current Github Integrations and also add Organization and Environment sync.

• Move the current integrations to react-hook-form
  • Show error on bad request
• Organization (UI)
• Environment (UI)
• Integrations Section (UI)
• Sync.ts backend
• Refactor
• Update docs

Type ✨

• Bug fix
• New feature
• Breaking change
• Documentation

Tests 🛠️

Will update soon

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[Salman2301]

#408

[gitguardian]

⚠️ GitGuardian has uncovered 9 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
-		Generic Password	9282dd0	docker-compose.dev.yml	View secret
-		Generic Password	9282dd0	docker-compose.dev.yml	View secret
-		Generic Password	9282dd0	.env.example	View secret
-		Generic Password	9282dd0	docker-compose.pg.yml	View secret
-		Generic Password	9282dd0	docker-compose.pg.yml	View secret
-		Generic High Entropy Secret	9282dd0	.env.example	View secret
-		Generic Private Key	f77942c	backend/e2e-test/routes/v3/secrets.spec.ts	View secret
-		Generic Private Key	f77942c	backend/e2e-test/routes/v3/secrets.spec.ts	View secret
-		Generic High Entropy Secret	f77942c	.env.test.example	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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[Salman2301]

integrations section for

1. Github Repo
2. Github Environment
3. Github Organization

Note that the schema being used was mongo. I updated the schema to match the current pg table. And also scope field moved outside from the metadata. Which Qovery integration was being used. Would be nice @vmatsiiako and @dangtony98 if you take a look.

[Salman2301]

Based on different scope, the secret will be synced

[Salman2301]

@akhilmhdh should I move to zod form resolver instead of yup?

[Salman2301]

This is ready to merge

[Grraahaam]

I haven't tested the PR yet, but it looks good. Great to have the feature and the docs at the same time 💪🏽

[maidul98]

Sorry about the delay @Salman2301. I will put this on the teams radar for next sprint

[dangtony98]

Hey @Salman2301!

I made some changes to the code. Can you help fix a few edge-cases:

1. When Scope > Repository Environment is selected, then the Environment dropdown should be disabled until the Repository field is selected.
2. The Repository Environment field should never display organizations in the dropdown (for some reason it shows me organizations when Repository is not selected.

Screenshot illustrating 1:

Screenshot illustrating 2:

[Salman2301]

Hey @Salman2301!

I made some changes to the code. Can you help fix a few edge-cases:

1. When Scope > Repository Environment is selected, then the Environment dropdown should be disabled until the Repository field is selected.
2. The Repository Environment field should never display organizations in the dropdown (for some reason it shows me organizations when Repository is not selected.

Both issue fixed with a simple disabled passed to select component.