Merge branch 'master' into flux-0.68

content/v2.0/account-management/multi-member/_index.md

@@ -1,16 +0,0 @@
----
-title: Manage multiple members
-description: >
-  View and manage multiple members in an InfluxDB Cloud account.
-weight: 4
-menu:
-  v2_0:
-    parent: Account management
-    name: Manage multiple members
----
-
-{{< cloud-name >}} accounts support multiple members in an organization.
-Collaborate with others using these features.
-By default, each member has full permissions on resources in your organization.
-
-{{< children >}}

content/v2.0/account-management/multi-member/invite-member.md

@@ -1,28 +0,0 @@
----
-title: Invite a member
-list_title: Invite a member
-description: >
-  Invite a member to collaborate in InfluxDB Cloud.
-weight: 103
-menu:
-  v2_0:
-    parent: Manage multiple members
-    name: Invite a member
----
-
-1. Navigate to the **Members** page under **Organizations** in the left navigation bar.
-   {{< nav-icon "org" >}}
-2. Under **Add a new member to your organization**, enter the email address of the member to invite.
-   (Members must be invited one at a time.)
-3. Click **Add & Invite**.
-
-An invitation with an activation link is sent to the specified email address.
-The activation link expires after 72 hours.
-
-Once activated, the new member is added as an **Owner** with permissions to read and write all resources.
-
-{{% warn %}}
-Currently, Cloud 2.0 has only one permission level: Owner.
-With Owner permissions, a member can delete resources and other members from your organization.
-Take care when inviting a member.
-{{% /warn %}}

content/v2.0/account-management/multi-member/remove-memberr.md

@@ -1,16 +0,0 @@
----
-title: Remove a member
-seotitle: Remove a member from your InfluxDB Cloud organization
-description: >
-  Remove a member from an InfluxDB Cloud organization.
-weight: 103
-menu:
-  v2_0:
-    parent: Manage multiple members
-    identifier: remove_member_cloud
----
-
-1. Navigate to the **Members** page under **Organizations** in the left navigation bar.
-   {{< nav-icon "org" >}}
-2. Click the {{< icon "delete" >}} next to the member you want to remove.
-3. Confirm the removal.

content/v2.0/account-management/multi-user/_index.md

@@ -0,0 +1,16 @@
+---
+title: Manage multiple users
+description: >
+  View and manage multiple users in an InfluxDB Cloud account.
+weight: 4
+menu:
+  v2_0:
+    parent: Account management
+    name: Manage multiple users
+---
+
+{{< cloud-name >}} accounts support multiple users in an organization.
+Collaborate with others using these features.
+By default, each user has full permissions on resources in your organization.
+
+{{< children >}}

content/v2.0/account-management/multi-user/invite-user.md

@@ -0,0 +1,27 @@
+---
+title: Invite a user
+list_title: Invite a user
+description: >
+  Invite a user to collaborate in InfluxDB Cloud.
+weight: 103
+menu:
+  v2_0:
+    parent: Manage multiple users
+    identifier: invite_user_cloud
+---
+
+1. Navigate to the **Users** page in the left navigation bar.
+2. Under **Add a new user to your organization**, enter the email address of the user to invite.
+   (Users must be invited one at a time.)
+3. Click **Add & Invite**.
+
+An invitation with an activation link is sent to the specified email address.
+The activation link expires after 72 hours.
+
+Once activated, the new user is added as an **Owner** with permissions to read and write all resources.
+
+{{% warn %}}
+Currently, Cloud 2.0 has only one permission level: Owner.
+With Owner permissions, a user can delete resources and other users from your organization.
+Take care when inviting a user.
+{{% /warn %}}

content/v2.0/account-management/multi-user/remove-user.md

@@ -0,0 +1,15 @@
+---
+title: Remove a user
+seotitle: Remove a user from your InfluxDB Cloud organization
+description: >
+  Remove a user from an InfluxDB Cloud organization.
+weight: 103
+menu:
+  v2_0:
+    parent: Manage multiple users
+    identifier: remove_user_cloud
+---
+
+1. Navigate to the **Users** page in the left navigation bar.
+2. Click the {{< icon "delete" >}} next to the user you want to remove.
+3. Confirm the removal.

content/v2.0/get-started.md

@@ -382,17 +382,17 @@ You are ready to [write or collect data](/v2.0/write-data).
 
 {{% note %}}
 #### Using the influx CLI after setting up InfluxDB through the UI
-To use the [`influx` CLI](/v2.0/reference/cli/influx) after setting up InfluxDB through the UI,
-use one of the following methods to provide your [authentication token](/v2.0/users/tokens/) to the CLI:
+To use the [`influx` CLI](/v2.0/reference/cli/influx) after setting up InfluxDB through the UI, provide your [authentication token](/v2.0/users/tokens/), which is automatically generated during the setup process. For instructions on viewing your token via CLI or UI, see [View tokens](/v2.0/security/tokens/view-tokens/).
 
-1. Pass your token to the `influx` CLI using the `-t` or `--token` flag.
-2. Set the `INFLUX_TOKEN` environment variable using your token.
+Use one of the following methods to provide your authentication token to the CLI:
+
+- Create a new InfluxDB connection configuration using the [`influx config create` command](/v2.0/reference/cli/influx/config/create/).
+- Pass your token to the `influx` CLI using the `-t` or `--token` flag.
+- Set the `INFLUX_TOKEN` environment variable using your token.
 
     ```bash
     export INFLUX_TOKEN=oOooYourAuthTokenOoooOoOO==
     ```
-3. Store your token in `~/.influxdbv2/credentials`.
-   _The content of the `credentials` file should be only your token._
 
 _See [View tokens](/v2.0/security/tokens/view-tokens/) for information about
 retrieving authentication tokens._
@@ -419,7 +419,10 @@ influx setup
    Enter nothing for an infinite retention period.
 7. Confirm the details for your primary user, organization, and bucket.
 
-InfluxDB is now initialized with a primary user, organization, and bucket.
+InfluxDB is now initialized with a primary user, organization, bucket, and authentication token. It has also create a config profile for you so that you don't have to add organization and token to every command. To view that config profile, use the [`influx config list`](/v2.0/reference/cli/influx/config) command.
+
+To continue to use InfluxDB via the CLI, you need the authentication token created during setup. To view the token, log into the UI with the credentials created above. (For instructions, see [View tokens in the InfluxDB UI](/v2.0/security/tokens/view-tokens/#view-tokens-in-the-influxdb-ui).)
+
 You are ready to [write or collect data](/v2.0/write-data).
 
 {{% note %}}
@@ -489,10 +492,7 @@ The primary differences between InfluxDB OSS 2.0 and InfluxDB Cloud 2.0 are:
 
 - [InfluxDB scrapers](/v2.0/write-data/scrape-data/) that collect data from specified
   targets are not available in {{< cloud-name "short" >}}.
-- {{< cloud-name "short" >}} instances are currently limited to a single organization with a single user.
-- **InfluxDB Cloud** does not support retrieving data from a file based CSV source
-  using the `file` parameter of the [`csv.from()`](/v2.0/reference/flux/functions/csv/from);
-  however you can use raw CSV data with the `csv` parameter.
+- {{< cloud-name "short" >}} instances are currently limited to a single organization.
 
 #### New features in InfluxDB Cloud 2.0
 

content/v2.0/reference/release-notes/flux.md

@@ -16,6 +16,22 @@ Though newer versions of Flux may be available, they will not be included with
 InfluxDB until the next InfluxDB v2.0 release._
 {{% /note %}}
 
+## v0.67.0 [2020-04-28]
+
+### Features
+- Planner Pattern interface supplies a set of ProcedureKind as root.
+- Initial prototype of a table-based Flux.
+- Evaluate and store "now" in execution dependencies for `tableFind()` to use.
+- Static analysis tool for listing entry points to Flux.
+- Pass context to rewrite rules in the planner.
+
+### Bug fixes
+- Pivot sends update watermark and processing time exactly once.
+- `system.time()` checks context for override.
+- Add bounds to alignTime tests.
+
+---
+
 ## v0.66.1 [2020-04-14]
 
 ### Bug fixes