ubicloud VS AWS SDK for Ruby

The docs still say the Elastic license is used but looking at https://github.com/ubicloud/ubicloud/blob/main/LICENSE it looks like the project might have switched to GNU Affero General Public License v3.0 in the last day.

At Ubicloud, we have 100% line and branch coverage that is mandated on every PR (https://github.com/ubicloud/ubicloud). We also have an E2E test suite that we run periodically and with every commit. We did not really feel like our tests are slowing us down, it actually makes us faster since we have a higher trust to the payload and many manual checks that would need to be done is safely skipped.

> Taken from here: https://ubicloud.com/

Am I the only one getting a certificate error browsing there?

Link to our project: https://github.com/ubicloud/ubicloud

We’re choosing Elastic V2 for three reasons: (1) We’re planning to monetize through a managed service and we’d like the license to support that, (2) Later if we change our mind, we think it’s easier on our users if we go from a restrictive license to a more permissive one, and (3) The Elastic V2 license is much simpler than its cousin, Server Side Public License (SSPL).

That said, Elastic V2 is a new license and doesn’t seem to as popular as SSPL. Also, some projects out there mix and match multiple licenses in their repo to be able to call themselves open source.

Any insights / feedback on Elastic V2 or software licenses in general?

In Ruby 3.2, "Fill.exists" was removed. brew will automatically install the most recent version of Ruby when you perform a brew install cocoapods, which is why you encounter this problem.

To those looking for this information officially, you can get it from the JSON files that describe every API that is in the SDK. Here's a link to that subtree in the Ruby SDK. You could write a parser to go through all the JSON files and grab this information, which is probably what others did.

Ruby SDK: https://github.com/aws/aws-sdk-ruby/pull/2553

Finally, for the purpose of this series, you will need to have installed Ruby, as well as the AWS SDK for Ruby.

AWS Lambda supports seven different languages in which you can code, including Ruby. Here, we will be using AWS Ruby-sdk to connect to DynamoDB.

We can re-use the same EC2 client stub response because Aws::EC2::Resource#instances implementation it's just a wrapper around the Aws::EC2::Client#describe_instances method, so the underlying EC2 API call is the same. Snippet code from https://github.com/aws/aws-sdk-ruby: