centersl/n8n-docs
1
0
Fork 0
mirror of https://github.com/n8n-io/n8n-docs.git synced 2026-03-27 09:28:43 +07:00
Code Issues Packages Projects Releases Wiki Activity

wip

Browse Source
This commit is contained in:
Deborah Barnard
2023-07-04 23:04:35 +01:00
parent 44a5852304
commit 2a7a66ec2a
4 changed files with 12 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
_snippets/source-control-environments/multi-instance-multi-branch-pros-cons.md
View File

@@ -3,5 +3,5 @@ The advantages of this pattern are:
* An added safety layer to prevent changes getting into your production environment by mistake. You have to do a pull request in GitHub to copy work between environments.
* It supports more than two instances.
The disadvantages is more manual steps to copy work between environments.
The disadvantage is more manual steps to copy work between environments.

BIN
docs/_images/source-control-environments/vc-multi-one.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 19 KiB

9
docs/source-control-environments/using/manage-variables.md
View File

@@ -1,16 +1,11 @@
---
title: Credential and variable values
title: Manage variables
description: Manage variable values in n8n using the API and source control.
---
# Manage variables
n8n doesn't sync credential and variable values with Git. You must set up the credentials manually when setting up a new instance. You can choose to set up variables manually, or [using the API](#manage-variables-using-the-api).
[TODO: cut mention of creds here]
!!! note "Coming soon: credential support with secret managers"
n8n is working on support for external secret managers to handle credentials. Once this feature is complete, n8n will support linking the secret manager to multiple instances.
n8n doesn't sync variable values with Git. You must set up the credentials manually when setting up a new instance. You can choose to set up variables manually, or [using the API](#manage-variables-using-the-api).
## Manage variables using the API

9
docs/source-control-environments/using/push-pull.md
View File

@@ -36,4 +36,13 @@ When you pull from Git to an n8n instance, the workflow owner may change. If the
## What gets committed
n8n commits the following to Git:
* Workflows, including their tags and the email address of the workflow owner. You can choose which workflows to push.
* Credential stubs (ID, name, type)
* Variable stubs (ID and name)
You can programmatically [Manage variables](/source-control-environments/using/manage-variables/) using the n8n API.
!!! note "Coming soon: credential support with secret managers"
n8n is working on support for external secret managers to handle credentials. Once this feature is complete, n8n will support linking the secret manager to multiple instances.