troposphere VS drone

Under the IaC category, in July 2023, AWS added loops to CloudFormation, finally ticking a box the community has been asking for since troposphere. I suspect that, in combination with the Terraform licensing changes, it may keep people using CloudFormation for a while longer.

Because ECS Compose-X uses Troposphere, I was able to create a very light and simple python library(https://github.com/JohnPreston/troposphere-awscommunity-applicationautoscaling-scheduledaction) to distribute the resource for other Troposphere users to re-use.

Written in house, but the library troposphere is the primary component of how it is built. Example stacks are here.

I am kind of going off topic here, but isn't the point of being an SA to be created with code services to deliver solutions at scale that are cost-effective? How in the hell can you do that when you can't write a simple Python template that generates code at 50 times the rate you can manually? How can you ever be expected to deploy a serverless solution if you can't write any code yourself? There has to be some level of proficiency there.

Wouldn't using troposphere[1] be easier?

[1] https://github.com/cloudtools/troposphere

You might have seen some tutorials on how to set up S3 buckets using the AWS Console. This works fine, but I'm a firm believer of managing your resources with code. I've chosen the native solution of AWS, called AWS CloudFormation. This makes it easier to reproduce the setup if I ever need to tear it down of move it to another account or region. Below is the full CloudFormation template, I've used a framework called Troposphere, a Python library that creates CloudFormation.

For CF for example I no longer write template in yaml or shudders json, and instead I use troposphere.

refer : https://github.com/cloudtools/troposphere

Drone (https://github.com/harness/drone) shell's all codes are deleted and replaced with new project (gitness) to retain Github Stars. What do you think?

I went to check on this, and it seems that https://github.com/harness/drone redirects to harness/gitness. I'm now very confused.

You can check the drone license or sentry license.

To use github my code would have to leave my server. I can build it myself using woodpecker. I used drone.io till they were bought out and went closed source then migrated to woodpecker-ci

A lot of people on reddit seem to recommend gitlab, or drone.io, but if you get on indeed and search for jobs there are tens of thousands of posts looking for people who know Jenkins and only a tiny fraction of job listings interested in any other ci framework. Is it worth investing time into anything else? It's my decision and while the other options seem more friendly I don't see any point in learning them if I'm not going to be able to use them in the future.

I personally use drone CI (https://drone.io) with the DroneExternalConfig plugin (https://github.com/0x1a8510f2/DroneExternalConfig).

Gitea + drone.io is what I am using. Very happy with the solution.

No 5000 build limit if you use Gitea/Gogs Ref: https://github.com/harness/drone/blob/master/service/license/load.go

I really should migrate to Gitea + drone.io

I'm really embarassed to say that I love docker-compose over K8s for its simplicity & effectiveness.But tools are reallly lacking.drone.io is like a docker-compose.yml. Simple, effictive & beautiful.