From 2db77822dc8c71cc0b1236a6600809de7c77cedd Mon Sep 17 00:00:00 2001 From: kelseiv <47797004+kelseiv@users.noreply.github.com> Date: Thu, 3 Sep 2020 17:28:05 -0700 Subject: [PATCH] Update content/v2.0/influxdb-templates/stacks/_index.md Co-authored-by: Russ Savage --- content/v2.0/influxdb-templates/stacks/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v2.0/influxdb-templates/stacks/_index.md b/content/v2.0/influxdb-templates/stacks/_index.md index 9a61775d4..b2dd28df5 100644 --- a/content/v2.0/influxdb-templates/stacks/_index.md +++ b/content/v2.0/influxdb-templates/stacks/_index.md @@ -104,7 +104,7 @@ You can do this for each of the stacks you are maintaining. Each time you make a For a complete example, check out the blog on [Building a GitOps Workflow with InfluxDB Templates](). -#### Automating deployment using Github Actions or CircleCI +#### Automate deployment using Github Actions or CircleCI Once you have a script to apply changes being made to your local instance, you can start to automate the deployment to other environments as needed. The InfluxDB CLI has the ability to maintain multiple [configuration profiles]() that makes it easy to issue commands against other InfluxDB instances. To apply the same script to a different InfluxDB instance, just change your active configuration profile using the `influx config set` command. You can also set the desired profile dynamically using the `-c, --active-config` flag.