Pipelines /
Update release flow
Required permission
Project > Pipelines > General > Update
Path parameters
projectId
string requiredID of the projectpipelineId
string requiredID of the pipelinestage
string requiredStage of the pipeline
Request body
- {object}
arguments
{object}A set of arguments that can be referenced in a template using '${args.argumentName}'.triggers
[array]- {object}
ref
stringA reference that can be used to access the output of this trigger in the template.vcsService
string requiredThe VCS provider to use.one ofbitbucket, gitlab, github, self-hosted, azureselfHostedVcsId
stringIf projectType is self-hosted, the ID of the self-hosted vcs to use.pattern^([A-Za-z0-9-]+\/[A-Za-z0-9-]+)|([0-9a-f]{24})$accountLogin
stringBy default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name.vcsLinkId
stringrepoUrl
string requiredURL of the Git repo that will trigger the template.pattern^(https:\/\/)?((www(\.[a-zA-Z0-9\-]{2,})+\.)?[a-zA-Z0-9\-]{2,})(\.([a-zA-Z0-9\-]{2,}))+(\/([a-zA-Z0-9\-._]{2,}))+?$branchRestrictions
[array]- stringpattern^[a-zA-Z/*0-9%\-.#_!'();,&=+]*$
prRestrictions
[array]- stringpattern^[a-zA-Z/*0-9%\-.#_!'();,&=+]*$
pathIgnoreRules
[array]An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax.- stringA path ignore rule, following `.gitignore` syntax. For example, `*.md` will ignore all files ending with `.md`.max length260
ciIgnoreFlags
[array]An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `["[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]`- stringA commit ignore flag.max length72
ciIgnoreFlagsEnabled
booleanisAllowList
booleanignoreDrafts
booleanIf `true`, draft pull requests from this repo will not trigger the template.options
{object}Options regarding how the template is run.concurrencyPolicy
stringDefines the concurrency behaviour of the template with respect to parallel runs.one ofallow, queue, forbidpaused
booleanIf `true`, the template will not run when triggered by git.gitops
{object}vcsService
string requiredThe VCS provider to use.one ofbitbucket, gitlab, github, self-hosted, azureselfHostedVcsId
stringIf projectType is self-hosted, the ID of the self-hosted vcs to use.pattern^([A-Za-z0-9-]+\/[A-Za-z0-9-]+)|([0-9a-f]{24})$accountLogin
stringBy default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name.vcsLinkId
stringLegacy key. Please used accountLogin instead.repoUrl
string requiredURL of the Git repo to sync the template with.pattern^(https:\/\/)?((www(\.[a-zA-Z0-9\-]{2,})+\.)?[a-zA-Z0-9\-]{2,})(\.([a-zA-Z0-9\-]{2,}))+(\/([a-zA-Z0-9\-._]{2,}))+?$branch
string requiredThe name of the branch to use.filePath
string requiredThe file path to the template in the repository. If using an existing template, it should be in JSON format.pattern^\/([a-zA-Z0-9-._]+\/)*[a-zA-Z0-9-._]+$$schema
stringrichInputs
[array]An array of rich UI override inputs for the Release Flow template.- (multiple options: oneOf)A node representing a rich UI override for the Release Flow template.
- {object}BranchCommitSelector input
kind
string requiredThe kind of input.one ofBranchCommitSelectorspec
{object} requiredThe specification for the BranchCommitSelector input.- {object}BuildSelector input
kind
string requiredThe kind of input.one ofBuildSelectorspec
{object} requiredThe specification for the BuildSelector input.apiVersion
string requiredproject
{object}spec
{object} required
OR
POST /v1/projects/{projectId}/pipelines/{pipelineId}/release-flows/{stage}
Example request
curl --header "Content-Type: application/json" \
--header "Authorization: Bearer NORTHFLANK_API_TOKEN" \
--request POST \
--data '{"triggers":[{"vcsService":"github","accountLogin":"github-user","repoUrl":"https://github.com/northflank-examples/remix-postgres-redis-demo","pathIgnoreRules":["README.md"],"ciIgnoreFlags":["[skip ci]"]}],"options":{"concurrencyPolicy":"allow","paused":false},"gitops":{"vcsService":"github","accountLogin":"github-user","repoUrl":"https://github.com/northflank-examples/remix-postgres-redis-demo","branch":"main"},"richInputs":[{"kind":"BranchCommitSelector","spec":{"required":false,"inputs":{"source":"build-service"},"outputs":{"branch":"TARGET_BRANCH","buildSha":"TARGET_COMMIT"}}}]}' \
https://api.northflank.com/v1/projects/{projectId}/pipelines/{pipelineId}/release-flows/{stage}
Example response
200 OK