secure-repo
argo
secure-repo | argo | |
---|---|---|
6 | 43 | |
237 | 14,374 | |
2.5% | 1.1% | |
2.8 | 9.8 | |
about 1 month ago | about 23 hours ago | |
Go | Go | |
GNU Affero General Public License v3.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
secure-repo
-
Show HN: Secure your public GitHub repository with automated security fixes
I am excited to share Secure-Repo, an open-source project that can easily secure your GitHub repository through automated security fixes. The project aims to automate common security fixes, so developers do not have to wade through documentation.
It does not require any App installation or onboarding steps, you can just enter your public repository and click on a button to improve security through automated pull requests.
I invite you to try Secure-Repo on your public repository using the hosted version at http://app.stepsecurity.io/securerepo and share your feedback.
Important open-source repositories have adopted the tool. Here are a few example pull requests created by the maintainers of Electron, Ruby, and GoogleCloudPlatform using this project.
Electron: https://github.com/electron/electron/pull/36363
-
Securing a GitHub repo is a ton of work
I've found StepSecurity's tooling helpful in getting my repos secured.
* https://app.stepsecurity.io/securerepo
-
Do you maintain a GitHub Action? Contribute to the SecureWorkflows project!
The problem we are trying to solve is to automatically calculate what the minimum GITHUB_TOKEN permissions should be for a given workflow. We are solving this problem by building a knowledge base of permissions needed by each GitHub Action. If you own a GitHub Action, contribute to the SecureWorkflows project by adding a YAML file describing the permissions your Action needs.
-
StepSecurity releases tool that it used to improve security of 30 critical open-source projects (including NodeJS, OpenSSL, Python, Rails, React Native)
List of merged pull requests for the 30 critical projects can be found here: https://github.com/step-security/secure-workflows/issues/462
- Secure GitHub Actions workflows by automatically updating the workflow (YAML) files
argo
-
StackStorm – IFTTT for Ops
Like Argo Workflows?
https://github.com/argoproj/argo-workflows
-
Creators of Argo CD Release New OSS Project Kargo for Next Gen Gitops
Dagger looks more comparable to Argo Workflows: https://argoproj.github.io/argo-workflows/ That's the first of the Argo projects, which can run multi-step workflows within containers on Kubernetes.
For what it's worth, my colleagues and I have had great luck with Argo Workflows and wrote up a blog post about some of its advantages a few years ago: https://www.interline.io/blog/scaling-openstreetmap-data-wor...
-
Practical Tips for Refactoring Release CI using GitHub Actions
Despite other alternatives like Circle CI, Travis CI, GitLab CI or even self-hosted options using open-source projects like Tekton or Argo Workflow, the reason for choosing GitHub Actions was straightforward: GitHub Actions, in conjunction with the GitHub ecosystem, offers a user-friendly experience and access to a rich software marketplace.
-
(Not) to Write a Pipeline
author seems to be describing the kind of patterns you might make with https://argoproj.github.io/argo-workflows/ . or see for example https://github.com/couler-proj/couler , which is an sdk for describing tasks that may be submitted to different workflow engines on the backend.
it's a little confusing to me that the author seems to object to "pipelines" and then equate them with messaging-queues. for me at least, "pipeline" vs "workflow-engine" vs "scheduler" are all basically synonyms in this context. those things may or may not be implemented with a message-queue for persistence, but the persistence layer itself is usually below the level of abstraction that $current_problem is really concerned with. like the author says, eventually you have to track state/timestamps/logs, but you get that from the beginning if you start with a workflow engine.
i agree with author that message-queues should not be a knee-jerk response to most problems because the LoE for edge-cases/observability/monitoring is huge. (maybe reach for a queue only if you may actually overwhelm whatever the "scheduler" can handle.) but don't build the scheduler from scratch either.. use argowf, kubeflow, or a more opinionated framework like airflow, mlflow, databricks, aws lamda or step-functions. all/any of these should have config or api that's robust enough to express rate-limit/retry stuff. almost any of these choices has better observability out-of-the-box than you can easily get from a queue. but most importantly.. they provide idioms for handling failure that data-science folks and junior devs can work with. the right way to structure code is just much more clear and things like structuring messages/events, subclassing workers, repeating/retrying tasks, is just harder to mess up.
-
what technologies are people using for job scheduling in/with k8s?
Argo Workflows + Argo Events
-
What are some good self-hosted CI/CD tools where pipeline steps run in docker containers?
Drone, or Tekton, Argo Workflows if you’re on k8s
-
job scheduling for scientific computing on k8s?
Check out Argo Workflows.
- Orchestration poll
- What's the best way to inject a yaml file into an Argo workflow step?
-
Which build system do you use?
go-git has a lot of bugs and is not actively maintained. The bug even affects Argo Workflow, which caused our data pipeline to fail unexpectedly (reference: https://github.com/argoproj/argo-workflows/issues/10091)
What are some alternatives?
machine - Machine is a workflow/pipeline library for processing data
temporal - Temporal service
DnsControl - Infrastructure as code for DNS!
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
Beehive - A flexible event/agent & automation system with lots of bees 🐝
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
reposaur - Open source compliance tool for development platforms.
flyte - Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
mysql-actions - MySQL Actions
StackStorm - StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html
functions-framework-dotnet - FaaS (Function as a service) framework for writing portable .NET functions
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.