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

add guardduty dependency #62

Merged
merged 2 commits into from
Sep 9, 2020
Merged

add guardduty dependency #62

merged 2 commits into from
Sep 9, 2020

Conversation

samscottchef
Copy link
Contributor

Signed-off-by: Sam Scott [email protected]

uncommented the GuardDuty add dependency

Description

I need the GuardDuty gem for adding a new resource in InSpec AWS

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New content (non-breaking change)
  • Breaking change (a content change which would break existing functionality or processes)

Checklist:

  • I have read the CONTRIBUTING document.

Signed-off-by: Sam Scott <[email protected]>
@@ -117,7 +117,7 @@ Gem::Specification.new do |spec|
# spec.add_dependency "aws-sdk-glue", "~> 1.0"
# spec.add_dependency "aws-sdk-greengrass", "~> 1.0"
# spec.add_dependency "aws-sdk-groundstation", "~> 1.0"
# spec.add_dependency "aws-sdk-guardduty", "~> 1.0"
spec.add_dependency "aws-sdk-guardduty", "~> 1.0"
Copy link

@rmoles rmoles Sep 8, 2020

Choose a reason for hiding this comment

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

I see the newest version of guardduty is at 1.31. Should we consider updating this to the latest?
Thoughts @skpaterson @samscottchef ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Seems worthwhile to me

Copy link

@Schwad Schwad left a comment

Choose a reason for hiding this comment

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

@samscottchef this looks good/reasonable enough to me 😄

Whenever we add/bump dependencies I usually ping @inspec/foundation-team-reviewers for a day to ensure we're not missing any knowledge i.e. "we can't add this dependency because x"! - So unless they raise something by tomorrow happy to approve.

Do concur with @rmoles about using 1.31 if possible 👍

Signed-off-by: Sam Scott <[email protected]>
@samscottchef
Copy link
Contributor Author

Latest commit updated to 1.31

Copy link
Contributor

@tas50 tas50 left a comment

Choose a reason for hiding this comment

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

Works for me

Copy link

@Schwad Schwad left a comment

Choose a reason for hiding this comment

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

Thanks for this! Got foundation team's eyes on it and I'm happy to merge 🎉

@Schwad
Copy link

Schwad commented Sep 9, 2020

(and by "me" I mean someone who's actually authorized to merge on this PR 😂 , probably @rmoles )

Copy link

@skpaterson skpaterson left a comment

Choose a reason for hiding this comment

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

Thanks @samscottchef !

@skpaterson skpaterson merged commit dd1754d into master Sep 9, 2020
@skpaterson skpaterson deleted the add_guardduty_gem branch September 9, 2020 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants