cloud-radar VS Espial

I'm the author of Cloud-Radar, a Cloudformation testing framework written in Python. I just released v0.7.0 which had some major user experience improvements and I wanted to share it with all of you.

But I think it's okay if you like Cloudformation. In fact, I have another project that you will love. I created a testing framework for Cloudformation templates called Cloud-Radar. It allows you to test your templates locally without credentials. https://github.com/DontShaveTheYak/cloud-radar

Final follow up ;)

If you like Cloudformation, you might be interested in my Cloudformation testing library.

https://github.com/DontShaveTheYak/cloud-radar

It's the most powerful Cloudformation testing framework that exists.

It allows you to unit test your Templates locally with out deploying resources. That also means you don't need valid AWS creds while unit testing.

If you are using cloudformation, I have a python testing library https://github.com/DontShaveTheYak/cloud-radar

It allows unit testing of cloudformation templates locally without needing aws credentials or deploying anything.

It also supports functional testing of cloudformation stacks once they are deployed.

Full guide on my blog https://la-tech.co/post/hypermodern-cloudformation/getting-s...

https://github.com/DontShaveTheYak/jenkins-std-lib A Jenkins shared library with a couple cool things like running GitHub Actions on Jenkins.

https://github.com/DontShaveTheYak/cloud-radar Unit and Functional testing of AWS Cloudformation templates. The unit testing part allows you to test locally without needing AWS creds.

https://github.com/DontShaveTheYak/sebs Stateful Elastic Block Storage was created so that you could make sure that a AWS ec2 instance always had the same EBS volume mounted to it. Really handy for a Ec2 instance in an ASG with a count of 1.

I created a tool called cloud-radar that would allow me to test the logic that is inside of a Cloudformation templates. Things like the conditionals and intrinsic functions. This all happens locally without deploying and worrying about credentials or assuming roles. You can take a template like this and test it like this:

Tangentially, I would recommend exporting your Pinboard collection periodically to somewhere safe. The service has gotten sketchy in the last year or two. I transitioned mine to a self-hosted instance of Espial.

An alternative, one that I began using a year ago after losing confidence in Pinboard is the self-hosted Espial - https://github.com/jonschoning/espial.

The visual presentation is a near complete clone of Pinboard. It also provides a route for Pinboard import.

Link repository - I use a self-hosted instance of Espial, but again the technology is unimportant. I mention this only because one of the philosophies of the Zettelkasten is to avoid the collector's fallacy where just by saving something you think you know it. So links go here if I might want to find it again in the future but I don't have time to think about it now or take notes on it into the ZK.

Saving URL's: For the most part, I don't like existing built-in bookmarking solutions in most browsers, because they seem to treat metadata cursorily or just ignore it. I've started using Espial which is a self-hosted Pinboard knock-off that allows me to tag and comment on URL's that I save.

you could run my self-hosted bookmarking site locally (which includes basic notes) https://github.com/jonschoning/espial

I actively avoid super general code in my Haskell applications.

Here's some code to add a bookmark in an api controller:

https://github.com/jonschoning/espial/blob/master/src/Handle...