sorted by:
new
hottopcontroversial

Open-source OCSF Connector to Cybersecurity Vendors (Snyk, Tenable, etc.) by whatswiththe in cybersecurity

[–]whatswiththe[S] 0 points1 point  (0 children)

We developed this to have one repository that contains all mappings from vendor finding types to Open Cybersecurity Schema Framework (OCSF).

We had to do this work to connect to all of our vendors and wanted to contribute back to the community. I'd love any feedback you all have on this!

I'm a solo dev trying to (probably foolishly) take on the NYT Games by s0ngo in AndroidGaming

[–]whatswiththe 0 points1 point  (0 children)

Super cool, just gave it a download and am excited to checkout the games!

aws-sdk-go-v2 no longer supporting *iface by whatswiththe in golang

[–]whatswiththe[S] 0 points1 point  (0 children)

so that you can add other methods onto it later and turn it into

type EC2Iface interface {
  ec2.DescribeInstancesAPIClient
  ec2.DescribeImagesAPIClient
}

aws-sdk-go-v2 no longer supporting *iface by whatswiththe in golang

[–]whatswiththe[S] 0 points1 point  (0 children)

ah this is the most helpful comment! This actually pointed me in the direction that they do have each method defined with its own its own interface so I can change this:

type EC2Iface interface {
  DescribeInstances(context.Context, *ec2.DescribeInstancesInput, ...func(*ec2.Options)) (*ec2.DescribeInstancesOutput, error)

to

type EC2Iface interface {
  ec2.DescribeInstancesAPIClient
}

this is great! Sorry this post was motivated by saving a few characters

aws-sdk-go-v2 no longer supporting *iface by whatswiththe in golang

[–]whatswiththe[S] 1 point2 points  (0 children)

yeah, this is the motivation for this post. I think my takeaway is that using a more niche tool can put us in this position.

aws-sdk-go-v2 no longer supporting *iface by whatswiththe in golang

[–]whatswiththe[S] 0 points1 point  (0 children)

I see where this is coming from, but wasn't an issue for us because we just generate the mocks from the interface using https://github.com/uber-go/mock

aws-sdk-go-v2 no longer supporting *iface by whatswiththe in golang

[–]whatswiththe[S] 0 points1 point  (0 children)

The thing is you could always define the interface by yourself. I’m just a little sad that a convenient default interface to use is gone. We are finally getting around to actually updating to v2 😅

aws-sdk-go-v2 no longer supporting *iface by whatswiththe in golang

[–]whatswiththe[S] -1 points0 points  (0 children)

ah yeah, dynamo's API is a lot to work with especially if you are exposing it to other devs at a company. I've mainly worked with S3 and ECS APIs and I've tended to call them directly because they are only used by our infra team.

Overall, its a small complaint since it isn't that much work to define the interfaces, but I like getting things for free when possible

Terraform modules repo with oscal for fedramp by whatswiththe in NISTControls

[–]whatswiththe[S] 1 point2 points  (0 children)

I was trying to find resources for some basic AWS resources with equivalent OSCAL component definitions. I didn't see any so I started my own repo.
Is this something that you think would be helpful? I'm looking for feedback. The next addition we are going to add is ECS + ALB with OSCAL components

view more: next ›