Improve utils/providerHelper.ts

[umrkhn]

Is your feature request related to a problem? Please describe.
Currently there is a lot of duplicated code as you can see below:

komiser/dashboard/utils/providerHelper.ts

Lines 1 to 57 in 5983512

	export type Provider =
	| 'aws'
	| 'gcp'
	| 'digitalocean'
	| 'azure'
	| 'civo'
	| 'kubernetes'
	| 'linode'
	| 'tencent'
	| 'oci'
	| 'scaleway'
	| 'mongodbatlas'
	| 'ovh'
	| 'pulumi'
	| 'terraform';
	type ProviderKey =
	| 'AWS'
	| 'GCP'
	| 'DIGITAL_OCEAN'
	| 'AZURE'
	| 'CIVO'
	| 'KUBERNETES'
	| 'LINODE'
	| 'TENCENT'
	| 'OCI'
	| 'SCALE_WAY'
	| 'MONGODB_ATLAS'
	| 'OVH'
	| 'PULUMI'
	| 'TERRAFORM';
	export const allProviders: { [key in ProviderKey]: Provider } = {
	AWS: 'aws',
	GCP: 'gcp',
	DIGITAL_OCEAN: 'digitalocean',
	AZURE: 'azure',
	CIVO: 'civo',
	KUBERNETES: 'kubernetes',
	LINODE: 'linode',
	TENCENT: 'tencent',
	OCI: 'oci',
	SCALE_WAY: 'scaleway',
	MONGODB_ATLAS: 'mongodbatlas',
	OVH: 'ovh',
	TERRAFORM: 'terraform',
	PULUMI: 'pulumi'
	};
	export type DBProvider = 'postgres' | 'sqlite';
	type DBProviderKey = 'POSTGRES' | 'SQLITE';
	export const allDBProviders: { [key in DBProviderKey]: DBProvider } = {
	POSTGRES: 'postgres',
	SQLITE: 'sqlite'
	};

Describe the solution you'd like
we can improve it by converting Provider and DBProvider into an enum as was suggested in the PR #1125 for IntegrationProvider

komiser/dashboard/utils/providerHelper.ts

Lines 57 to 62 in 5983512

	export enum IntegrationProvider {
	SLACK = 'slack',
	WEBHOOK = 'webhook'
	}

Why should we implement this?
It would reduce code duplication and runtime errors, for ex: instead of hard-coding the values like 'postgres' we can import the enum and reference the property name as shown in the screenshot below:

Would you like to work on this issue?
Yes, once approved I'll start working on it.

[github-actions]

Hey, thank you for opening your first Issue! 🙂 While a Tailwarden team member takes a look at your issue we would like to invite you to join our official Discord server, where you can interact directly with other contributors and Tailwarden team members. Link here: https://discord.tailwarden.com