While resources are fundamentally the same across clouds (i.e. they're all VMs, they all have firewalls etc), they are vastly different concepts and have different feature sets. It's almost impossible to do a like for like api call between two providers.
However, you can develop cloud agnostic modules that you can then consume, which allows for a decent cloud-agnostic experience.
Heh, I struggle figure out what is a real review and what is a paid for ad. It's sad to the point where I've pretty much given up because of the sheer amount of time it would take to do the research. Instead I opt to go for Amazon's competitors (e.g. Currys and Argos for us in the UK) and pick something there. They're a little more vetted, and less likely to be knock off or something.
Sure, and that's probably best. In my original comment, I specifically mentioned that what the FBI is asking for is reasonable providing there is a warrant, which would imply that they're gathering evidence lawfully.
> why not just do a bash script with a switch in it?
Because with bash scripts you'd be re-inventing the wheel when it comes to dependencies, among other things.
Make certainly might not be the right tool for having a bunch of "dev commands" that aren't targets/recipes, but bash isn't it either. There is plenty of task runners that allow you to have a single source of truth for dev commands.
Octopus Deploy and TeamCity are horrific. Jenkins is hilarious better despite all of its flaws. Concourse CI has a higher learning curve than Jenkins (at least for users, not necessarily admins), but once you get it, it's definitely a good contender. CircleCI is great!
I'm European-Kurd, and had to travel to Kurdistan Region (northern Iraq) for my sister's wedding a few years before I had to go to the US. I was denied my ESTA without a refund (it was $20 iirc, so not a huge amount but as someone who had just graduated, every penny counted for me) due to this exemption. Had to get a full visitors visa to go which took a lot longer, and was way more expensive. The exemption, which was put in place due to ISIS in 2013, seems reasonable though unfortunate.
I don't understand the love for hCaptcha. The only thing it has going for it is being outside of the Google brand and that it is cheaper. Outside that, we don't know that they don't do the same shady shit Google does, they're equally as bad as reCaptcha, and they're equally inaccessible.
Note: due to the design of PM, the search is done client-side rather than server-side. It's not an excuse but at the very least, full-text search is harder.
Great, so now link each request across services, combined with the timings of each individual component within each service. LogInsights is for logging, not tracing. Logging is not a replacement for tracing.
Using GitHub's stale bot you can set it to ignore labelled issues, and so it's up to maintainer to label things correctly. Once the maintainer does so, stale bot won't touch it.
That's right. It's all use-case based. Indiscriminately closing issues automatically is definitely wrong. Automatically closing issues that cannot be reproduced or have other issues is a perfect use-case for stale bot.
However, you can develop cloud agnostic modules that you can then consume, which allows for a decent cloud-agnostic experience.