feat: add Integration model

[bogdanoniga]

Integration model is meant to be a base model for service integrations (e.g. AWS, GCP, etc.). It serves two main functions:

• Manage the service integrations and related credentials within the UI;
• Manage the actions/commands to be performed per service integration;
• Map assets to service integrations in a similar way as Source model does.

Each service integration has its own particularities and actions, therefore, this model will be inherited and extended per service integration's needs.

[DDuarte]

I like the idea but not the implementation, in particular the hardcoded values in IntegrationType - it doesn't allow for composability.

IMO it would be better if each "integration" app registered itself on init, similar to how the django apps already work. It could even be an extended version of AppConfig with metadata relevant for integrations.

[bogdanoniga]

I like the idea but not the implementation, in particular the hardcoded values in IntegrationType - it doesn't allow for composability.

IMO it would be better if each "integration" app registered itself on init, similar to how the django apps already work. It could even be an extended version of AppConfig with metadata relevant for integrations.

IntegrationType is not an important field, we can rely on the child name. I'll remove the field

[bogdanoniga]

I was thinking to have an extended Integration model part of new django applications (if required) and match the application particularities with an extended list of fields. For instance, a new module named django-github, meant to sync data from Github, will extend the Integration model to match Github particularities and actions. Therefore, the credentials will be different for Github compared to other services (e.g. AWS) which requires new fields to be added

[bogdanoniga]

I like the idea but not the implementation, in particular the hardcoded values in IntegrationType - it doesn't allow for composability.

IMO it would be better if each "integration" app registered itself on init, similar to how the django apps already work. It could even be an extended version of AppConfig with metadata relevant for integrations.

With this proposal I would like to dynamically manage the integrations at application level at any time after deployment not as an integration config at init phase. I'm trying to move away from the current approach which defines integration credentials as env vars to a more dynamic way of creating and managing integrations via UI

[bogdanoniga]

As an example, https://github.com/surface-security/django-github uses Integration model as part of the testapp

[bogdanoniga]

somebody has a bit of free time to review this PR?