argo-rollout

module

v0.3.0 Latest Latest Go to latest Published: Jul 29, 2026 License: MIT

README ¶

argo-rollout

Getting started

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom!

Add your files

Create or upload files
Add files using the command line or push an existing Git repository with the following command:

cd existing_repo
git remote add origin https://gitlab.com/gitlab-org/ci-cd/runner-tools/argo-rollout.git
git branch -M main
git push -uf origin main

Integrate with your tools

Set up project integrations

Collaborate with your team

Test and Deploy

Use the built-in continuous integration in GitLab.

Editing this README

When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to makeareadme.com for this template.

Suggestions for a good README

Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

Name

Choose a self-explaining name for your project.

Description

Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

Badges

On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

Visuals

Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

Installation

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.

Contributing

State if you are open to contributions and what your requirements are for accepting them.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

Authors and acknowledgment

Show your appreciation to those who have contributed to the project.

License

For open source projects, say how it is licensed.

Project status

If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

Directories ¶

?	: This menu
/	: Search site
f or F	: Jump to
y or Y	: Canonical URL

Path	Synopsis
flows
cmd/bundle command Command bundle assembles the modular Starlark deploy program into the single self-contained gems/gitlab-deploy-driver-argo-rollouts/scripts/deploy.star that kas runs.	Command bundle assembles the modular Starlark deploy program into the single self-contained gems/gitlab-deploy-driver-argo-rollouts/scripts/deploy.star that kas runs.
integration_test
cmd/autoflow-driver command autoflow-driver kicks off one AutoFlow workflow run via the AutoFlow.StartWorkflow gRPC on kas's API server, optionally passing the workflow's named kwargs (--kwargs-file).	autoflow-driver kicks off one AutoFlow workflow run via the AutoFlow.StartWorkflow gRPC on kas's API server, optionally passing the workflow's named kwargs (--kwargs-file).
cmd/internal/autoflow_rpc
pkg
api/function Package function defines the public contracts kas injects into the CD Functions library: the seams through which a built-in Function reaches a resource it cannot construct for itself.	Package function defines the public contracts kas injects into the CD Functions library: the seams through which a built-in Function reaches a resource it cannot construct for itself.
gitlabfunctions Package gitlabfunctions implements the gitlab-function AutoFlow module: the bridge that lets a Starlark workflow call this repo's built-in CD Functions with load("module:gitlab-function", "run") then run(function="builtin://gitlab_project.read_files", inputs={...}).	Package gitlabfunctions implements the gitlab-function AutoFlow module: the bridge that lets a Starlark workflow call this repo's built-in CD Functions with load("module:gitlab-function", "run") then run(function="builtin://gitlab_project.read_files", inputs={...}).
internal/function Package function holds helpers shared across the builtin function implementations: GitLab client construction and the ErrNotFound sentinel (for gitlab_project.* Functions), the VersionedFile/CommitAction commit-IO types and files-input reader (for the manifest.* Functions), and JSONL output writing (for all).	Package function holds helpers shared across the builtin function implementations: GitLab client construction and the ErrNotFound sentinel (for gitlab_project.* Functions), the VersionedFile/CommitAction commit-IO types and files-input reader (for the manifest.* Functions), and JSONL output writing (for all).
internal/function/argopromote Package argopromote implements the argo.promote builtin function: advance an Argo Rollout past one canary pause point, idempotently.	Package argopromote implements the argo.promote builtin function: advance an Argo Rollout past one canary pause point, idempotently.
internal/function/argosync Package argosync implements the argo.sync builtin function: set an Argo CD Application's spec.source.targetRevision and trigger a sync.	Package argosync implements the argo.sync builtin function: set an Argo CD Application's spec.source.targetRevision and trigger a sync.
internal/function/commit Package commit implements the gitlab_project.commit builtin function: create a commit with one or more file changes on a branch in a GitLab project.	Package commit implements the gitlab_project.commit builtin function: create a commit with one or more file changes on a branch in a GitLab project.
internal/function/functiontest Package functiontest holds test helpers shared by the builtin gitlab_project.* function tests: an httptest-backed GitLab client and a JSONL output-file parser.	Package functiontest holds test helpers shared by the builtin gitlab_project.* function tests: an httptest-backed GitLab client and a JSONL output-file parser.
internal/function/k8sget Package k8sget implements the k8s.get builtin function: a generic, idempotent read of a single Kubernetes object, identified by api_version, kind, (optional) namespace, and name.	Package k8sget implements the k8s.get builtin function: a generic, idempotent read of a single Kubernetes object, identified by api_version, kind, (optional) namespace, and name.
internal/function/manifest Package manifest is the shared machinery the manifest.* CD Functions use to mutate Kubernetes GitOps manifests by editing a structured YAML document model, never by splicing strings into manifest text.	Package manifest is the shared machinery the manifest.* CD Functions use to mutate Kubernetes GitOps manifests by editing a structured YAML document model, never by splicing strings into manifest text.
internal/function/pinimages Package pinimages implements the manifest.pin_images builtin function: pin service artifact images into their Kubernetes workload manifests by editing a structured document model, never by splicing strings into manifest text.	Package pinimages implements the manifest.pin_images builtin function: pin service artifact images into their Kubernetes workload manifests by editing a structured document model, never by splicing strings into manifest text.
internal/function/readfile Package readfile implements the gitlab_project.read_files builtin function: read one or more files from a GitLab project at a Git ref.	Package readfile implements the gitlab_project.read_files builtin function: read one or more files from a GitLab project at a Git ref.
internal/function/setrollingstrategy Package setrollingstrategy implements the manifest.set_rolling_strategy builtin function: set a service's Argo Rollout to a rolling update strategy by editing a structured document model, never by splicing strings into manifest text.	Package setrollingstrategy implements the manifest.set_rolling_strategy builtin function: set a service's Argo Rollout to a rolling update strategy by editing a structured document model, never by splicing strings into manifest text.