Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[analyze] Add Analyzer for Mailgun #3206

Merged
merged 4 commits into from
Sep 12, 2024

Conversation

abmussani
Copy link
Contributor

Description:

Implemented Analyzer interface for Mailgun.

Checklist:

  • Tests passing (make test-community)?
  • Lint passing (make lint this requires golangci-lint)?

@abmussani abmussani requested a review from a team as a code owner August 9, 2024 10:48
@abmussani abmussani changed the title Add Analyzer for Mailgun [analyze] Add Analyzer for Mailgun Aug 12, 2024
Comment on lines 51 to 58
apiResource := analyzers.Resource{
Name: "Mailgun API Key",
FullyQualifiedName: "Mailgun API Key",
Type: "api key",
Metadata: map[string]any{
"domains_count": info.TotalCount,
},
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we need to differentiate this resource somehow? Or is it okay for all keys (across all accounts) to have access to this Mailgun API Key resource?

Since we're adding the domains_count here it seems like it's specific to this key.

domains will be added as resource in bindings and permissions.
updated the test.
@mcastorina mcastorina merged commit 57e5812 into trufflesecurity:main Sep 12, 2024
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants