Thomas/event service

[Tom-Caz]

Description

• Converted event service API from python to NextJS API routes
• I kept the naming conventions the same from the previous API. API uses camelCase (i.e eventTags), while DB uses snake_case (i.e event_tags).

Before pushing to Prod

• Make sure to add a on cascade to the prod DB for event_tags, industry_tags, and pinned_events. The SQL commands to do this are on the test DB
• Add in EVENT_AUTH_SERVICE_URL and EVENT_MASTER_TOKEN env variables

Battlepass

• For some reason, the battlepass-service is unformatted and prettier really wants to format it, so thats why it's there. I tried to remove it but our tests auto-format it on commit.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pointr	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 2, 2024 7:46pm

7 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
dashboard	⬜️ Ignored (Inspect)	Visit Preview		Sep 2, 2024 7:46pm
interim	⬜️ Ignored (Inspect)	Visit Preview		Sep 2, 2024 7:46pm
podium	⬜️ Ignored (Inspect)	Visit Preview		Sep 2, 2024 7:46pm
recruitment	⬜️ Ignored (Inspect)	Visit Preview		Sep 2, 2024 7:46pm
sso	⬜️ Ignored (Inspect)	Visit Preview		Sep 2, 2024 7:46pm
ui-kit-2023-storybook	⬜️ Ignored (Inspect)	Visit Preview		Sep 2, 2024 7:46pm
www-2023	⬜️ Ignored (Inspect)	Visit Preview		Sep 2, 2024 7:46pm

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9632465	Triggered	Generic Password	6c0d9b428e533585543e021f238a964e74c8cf89	apps/event-service/configs/env.local.yml	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}