humbug VS pulumi-aws

Once you set up an integration and instrument your code, you can access your user reports at https://bugout.dev. This gives you a live view of what your users are experiencing:

If you would like support for another programming language, please create an issue.

Hello everyone, I’m Sophia, founder of Bugout.dev.

I started off as a professional ballerina, and entered technology later in my working life - through the OpenAI Scholars program. My co-founder, Neeraj (zomglings on HN), is a mathematician and now programmer.

When I was learning how to code I kept running into issues. I found Stackoverflow and GitHub issues hard to navigate, often leading me to outdated solutions to the problems I was experiencing. That experience made me want a product that would collect crashes and immediately let the creators of the software I was using know about the issue. And when they or their community had fixed the issue, they could notify me about that and direct me to a public site detailing the solution.

Over time, this idea evolved and resulted in Bugout.dev. Bugout makes it easy for creators of developer tools to collect usage metrics and crash reports from their users. This applies equally well to libraries, command line utilities, and APIs.

We're advocates of ethical data collection, and all reports are collected with clear user consent. Maintainers can also comply with GDPR requests for access and deletion with a single API call each.

We are also building a public knowledge base of issues and solutions from open source projects. We were inspired by rustc error messages in this and how they point users to documentation that can help you resolve compiler errors. Projects integrating with Bugout can link users to the knowledge base using a search query, which allows them to direct users to solutions customized to operating system, library version, and even compiler/runtime version.

We support developer tools written in Python and in Go - we just launched the Go library this week!

Please check out our GitHub page: https://github.com/bugout-dev/humbug. We would greatly appreciate your feedback.

Understanding how your users experience your software is always difficult. It is especially difficult if we're talking about a developer tool like a library or command line utility.

Devtool maintainers have to rely on GitHub issues and IRC/Slack/Discord to talk with their users. They miss out the experience of the majority of their users, who never build up the motivation to create an issue or post a message on Slack.

Humbug addresses this problem. It collects developer tool usage reports and crash reports in a principled manner, only with the end user's full consent. Individuals or teams that maintain developer tools can use these reports to identify issues in their software, prioritize features, and in general improve their users' experience.

You can find a lot more information on GitHub: https://github.com/bugout-dev/humbug

Here is a short YouTube video showing how Humbug works: https://www.youtube.com/watch?v=-k2c8o_sXC4

Humbug is free to use for small projects. I hope you find it useful.

If you would like to discuss your use case in greater detail, I would love to speak with you in the comments. You can also reach me by email (check my profile).

Thank you! Created an issue: https://github.com/bugout-dev/humbug/issues/31

We have taken a big step forward this week with the release of Humbug, which helps developer tool maintainers collect usage and crash reports from their users only with their full consent.

Sure, but the providers for some of the biggest platforms are maintained by HashiCorp[1] - like the AWS, Azure, GCP, and Kubernetes providers[2], and it appears the Pulumi AWS provider (for example) _does_ use the Terraform AWS provider, even to this day[3].

1. https://developer.hashicorp.com/terraform/registry/providers... - "official" providers are maintained by HashiCorp

2. https://registry.terraform.io/browse/providers?tier=official - The filtered list of "official" providers maintained by HashiCorp

3. https://github.com/pulumi/pulumi-aws/tree/008c4360bc9fc24303... - Just prove it to myself, I can see the `upstream` git submodule, which embeds pulumi/terraform-provider-aws, which is a fork of hashicorp/terraform-provider-aws, although the repo was not created as a fork in Github, so it is not marked as a "fork" and so I have to compare commit histories to tell that it is a fork.

>Isn't pulumi aws just terraform under the hood still?

It depends.

The AWS "Classic" provider uses the terraform provider [1].

The AWS "Native" provider does not, and instead uses the AWS Cloud Control API [2].

[1]: https://github.com/pulumi/pulumi-aws

[2]: https://github.com/pulumi/pulumi-aws-native

Pulumi uses terraform providers to schematize the CRUD options for some cloud providers. Part of the difficulty with any infrastructure as code offering is that your favourite cloud provider doesn't always provide a full API spec, so we need to somehow figure out what resources can be created, what parameters are available to those resources etc. We take the terraform provider, look at the available operations for that provider and then turned it into a Pulumi schema, which can then be read by the Pulumi engine. If you take a look here you can actually see that generated schema for AWS.