https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/Recent content in Core onHugo -- gohugo.ioen-USSat, 09 Jan 2021 08:48:45 +0000https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/action/Fri, 11 Apr 2025 15:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/action/Description An Updatecli action defines what happens after a change is detected and validated. While Updatecli’s sources find changes (like a new version), and targets define where to apply them (like a file), actions describe what to do next—such as creating a pull request. Parameters Name Type Description Required disablepipelineurl boolean kind string kind specifies the actions resource kind scmid string spec object spec specifies parameters for a specific actions kind title string Examples In the follow example, we define an action that creates a pull request on GitHub when Updatecli detected outdated version of golangci-lint in GitHub action workflow files.https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/compose/Sun, 01 Oct 2023 12:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/compose/Description The updatecli compose feature allows specifying a list of updatecli policies to enforce. This is useful when applying the same policies on multiple repositories. By default, it relies on a file named "updatecli-compose.yaml" such as in the follow example: updatecli-compose.yaml policies: - name: Local Updatecli Website Policies config: - updatecli/updatecli.d/ - name: Handle Nodejs version in githubaction policy: ghcr.io/updatecli/policies/policies/nodejs/githubaction:latest values: - updatecli/values.d/scm.yaml - updatecli/values.d/nodejs.yaml Running updatecli compose apply would enforce the state defined in each of the policieshttps://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/shareandreuse/Sun, 01 Oct 2023 12:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/shareandreuse/Description As the number of updatecli policies increases, more and more, we realize that we need the ability to scale updatecli. Somewhere between what we have now, duplicated manifest(s) for each Git repository, and the Autodiscovery feature. We want to reuse updatecli policies across many projects. We want to write updatecli policies once and reuse them everywhere. For example: Enforcing the same Golang version used at the GitHub organization.https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/autodiscovery/Sun, 09 Jan 2022 15:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/autodiscovery/Description In the lifecycle of a software project, dependencies are everywhere. From that third application used to lint our code, the tool used to build our documentation website, or the container image used to distribute our application. As the project grows, the number of dependencies grows as long. Some dependencies are context-dependent, and others are expressed using a standard data structure. Updatecli is a great tool to handle both situations.https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/condition/Sat, 09 Jan 2021 15:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/condition/Description A "condition" stage defines whether to run the "Target" stage stage of a pipeline. It runs a check (depending on the resource kind) that returns a boolean indicating its success (true) or failure (true). Please look at each kind of resource (shell, file, etc.) for details about "how is the success/failure determined?". Parameters Name Type Description Required dependson array “dependson” allows to specify the order of execution of resources.https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/source/Sat, 09 Jan 2021 15:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/source/Description The "source" stage retrieves information from a third "resource" like a file, or an API and then uses that information in later stages. Parameters Name Type Description Required dependson array “dependson” allows to specify the order of execution of resources. It accepts a list of rules like “(resourceType#)resourceId(:booleanOperator)”. The resourceType is optional and can be one of “condition”, “source” or “target” By default the resourceType is the current resource typehttps://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/target/Sat, 09 Jan 2021 15:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/target/Description The "target" stage is updated if the necessary "resource", like a file based on information retrieved from a source. This happens provided all condition checks succeed. Parameters Name Type Description Required dependson array “dependson” allows to specify the order of execution of resources. It accepts a list of rules like “(resourceType#)resourceId(:booleanOperator)”. The resourceType is optional and can be one of “condition”, “source” or “target” By default the resourceType is the current resource typehttps://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/transformer/Sat, 09 Jan 2021 15:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/transformer/Description The "transformers" parameter can be used by any stage definition as a "source", "condition", or "target". A "transformers" object contains a list of transformers. Each kind of transformer rules applies a string manipulation like adding or removing characters. source Source returns information modified by a list of transformers. condition A condition receives information from the source then modifies that value using transformers before using it in the resource.https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/configuration/Tue, 13 Oct 2020 15:21:01 +0200https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/configuration/Updatecli requires a configuration file, or "manifest", which describes the update pipeline. A manifest describes the "what", the "when", and the "where" of the update pipeline. What The "what" is the "source" and defines what piece of information we’re looking for, such as the latest application release version, a docker image tag, etc. When The "when" is a "condition", if the condition is satisfied then the target is updated.https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/versionfilter/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-2806--amazing-golick-2d0138.netlify.app/docs/core/versionfilter/versionFilter allows to specify the kind of version retrieved from a resource and its version pattern. Default value is "latest" as we want to retrieve the newest version from a resource. latest If kind is set to latest then no need to specify the patter as we gonna retrieve the newest version from the resource. Example sources: kubectl: kind: githubRelease spec: owner: "kubernetes" repository: "kubectl" token: "{{ requiredEnv .github.token }}" username: "john" versionFilter: kind: latest transformers: - trimPrefix: "kubernetes-" Return the latest Github release and remove "kubernetes-" from it.