lifeway / cloudgenesis Goto Github PK

On a fresh build, I get a dirty working directory in cf-gitops-scala-common/ and s3-event-demux/. Copying the gitignore stanzas from s3-event-handlers/ should prevent that.

attachments is deprecated for the new blocks-style. It's pretty trivial to convert.

I also notice slack-message-building is currently duplicated in 3/4 places throughout this project, having a central function/library would make this work much easier.

I guess bintray is no more. Using www.scala-sbt.org/sbt-rpm.repo seems to work.

When someone opens a PR in the GitOps repo managed by CG, CG could run through every deploy it would do but with --no-execute-changeset and then post the JSON output of describe-changeset calls back to the originating PR. This would make the PRs incredibly reviewable, as you can see exactly the infra changes that would occur if merged.

I think this would require re-architecting the S3 side of things somehow. IIUC, there is presently a single bucket with a single state that triggers a deploy when changed. We would somehow need to synchronize the branch's version of things in a way that accurately triggers on what differs, but without actually persisting. If there's a less disruptively way to add this feature, do let me know.

This would also not work if you push a PR that has dependent changes across stacks -- though I don't think that's particularly well-supported even when actually executing the deploys today.

The python tests spam a lot of Resource Warning lines. These could be silenced with warnings.simplefilter as part of setUp.

A lot of this project is devoted to the CodeBuild pipeline. However, I find it much nicer to skip all of that and simply have my GitOps repo's GitHub Action upload the changed files directly to the S3 Bucket.

I'd like to make all those resources conditional, so it's easy to deploy without them for such a setup.

AWS won't allow deployment of Lambdas on 2.7 any more. The code here appears mostly 3-compatible, with just urllib imports needing to change.

Hi there-

This seems to be the only tool around for GitOps that is CloudFormation-focused and not coupled to Kubernetes. I'm using it in a project and it works well, but there are various things I've had to fix or want to extend.

I'm curious if this project is still being maintained because, if it is, I would try to contribute and craft my changes to increase the chances of review and acceptance. If it's not, I would probably fork and start making much more substantial (or messy) changes without concern for eventually being accepted upstream.

Thanks!