From f538505ef11dcf91cea0dbc9036e1dfd924476e9 Mon Sep 17 00:00:00 2001 From: Scott Anderson Date: Wed, 29 Apr 2020 10:22:10 -0600 Subject: [PATCH 1/7] added flux 0.67.0 to flux changelog --- content/v2.0/reference/release-notes/flux.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/content/v2.0/reference/release-notes/flux.md b/content/v2.0/reference/release-notes/flux.md index daf7f5630..da2c34673 100644 --- a/content/v2.0/reference/release-notes/flux.md +++ b/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 From e6f234bb81aae426e79eeeb9376ea528359e26bf Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Wed, 29 Apr 2020 10:24:15 -0700 Subject: [PATCH 2/7] Add clarification about token creation during setup and link to vieiwng tokens doc (adresses #985 ) --- content/v2.0/get-started.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/v2.0/get-started.md b/content/v2.0/get-started.md index 21ef2a565..f06b44dba 100644 --- a/content/v2.0/get-started.md +++ b/content/v2.0/get-started.md @@ -381,8 +381,9 @@ 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/). + +Use one of the following methods to provide your authentication token to the CLI: 1. Pass your token to the `influx` CLI using the `-t` or `--token` flag. 2. Set the `INFLUX_TOKEN` environment variable using your token. @@ -418,7 +419,7 @@ 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. (For instructions on viewing your token via CLI or UI, see [View tokens](/v2.0/security/tokens/view-tokens/).) You are ready to [write or collect data](/v2.0/write-data). {{% note %}} From 084f1a2512375eaa896ef4f64a02371ae661b100 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Wed, 20 May 2020 14:06:20 -0700 Subject: [PATCH 3/7] Add details on getting token to CLI setup instructions --- content/v2.0/get-started.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/v2.0/get-started.md b/content/v2.0/get-started.md index f06b44dba..cdee2e640 100644 --- a/content/v2.0/get-started.md +++ b/content/v2.0/get-started.md @@ -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, bucket, and authentication token. (For instructions on viewing your token via CLI or UI, see [View tokens](/v2.0/security/tokens/view-tokens/).) +InfluxDB is now initialized with a primary user, organization, bucket, and authentication token. + +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 %}} From 28f3dfda8f46521656ba818cf36db54327c519b0 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Wed, 20 May 2020 14:11:42 -0700 Subject: [PATCH 4/7] Remove credentials option, add info about `influx config create` --- content/v2.0/get-started.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/content/v2.0/get-started.md b/content/v2.0/get-started.md index cdee2e640..23a982e69 100644 --- a/content/v2.0/get-started.md +++ b/content/v2.0/get-started.md @@ -385,14 +385,13 @@ To use the [`influx` CLI](/v2.0/reference/cli/influx) after setting up InfluxDB Use one of the following methods to provide your authentication token to the CLI: -1. Pass your token to the `influx` CLI using the `-t` or `--token` flag. -2. Set the `INFLUX_TOKEN` environment variable using your token. +- 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._ @@ -421,7 +420,7 @@ influx setup InfluxDB is now initialized with a primary user, organization, bucket, and authentication token. -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).) +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). From 5b52335bc2662f9300071a7af537a035a4acadfe Mon Sep 17 00:00:00 2001 From: Russ Savage Date: Thu, 21 May 2020 10:53:57 -0700 Subject: [PATCH 5/7] fix(getting-started): minor edits --- content/v2.0/get-started.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/content/v2.0/get-started.md b/content/v2.0/get-started.md index 23a982e69..8212ca83b 100644 --- a/content/v2.0/get-started.md +++ b/content/v2.0/get-started.md @@ -418,7 +418,7 @@ 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, bucket, and authentication token. +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).) @@ -488,9 +488,6 @@ 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. #### New features in InfluxDB Cloud 2.0 From a828d867b2a06e7f6f0c388d5efc2b365eaf7c3b Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Wed, 27 May 2020 08:39:47 -0700 Subject: [PATCH 6/7] Remove single user reference --- content/v2.0/get-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v2.0/get-started.md b/content/v2.0/get-started.md index 8212ca83b..0c38d0e10 100644 --- a/content/v2.0/get-started.md +++ b/content/v2.0/get-started.md @@ -487,7 +487,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. +- {{< cloud-name "short" >}} instances are currently limited to a single organization. #### New features in InfluxDB Cloud 2.0 From 62ef1eecd76bd6544c0db70d97bad38815ea2f0e Mon Sep 17 00:00:00 2001 From: pierwill Date: Tue, 26 May 2020 11:07:50 -0700 Subject: [PATCH 7/7] Update terminology in Cloud Multi-user docs Fixes #1066 --- .../account-management/multi-member/_index.md | 16 ----------- .../multi-member/invite-member.md | 28 ------------------- .../multi-member/remove-memberr.md | 16 ----------- .../account-management/multi-user/_index.md | 16 +++++++++++ .../multi-user/invite-user.md | 27 ++++++++++++++++++ .../multi-user/remove-user.md | 15 ++++++++++ 6 files changed, 58 insertions(+), 60 deletions(-) delete mode 100644 content/v2.0/account-management/multi-member/_index.md delete mode 100644 content/v2.0/account-management/multi-member/invite-member.md delete mode 100644 content/v2.0/account-management/multi-member/remove-memberr.md create mode 100644 content/v2.0/account-management/multi-user/_index.md create mode 100644 content/v2.0/account-management/multi-user/invite-user.md create mode 100644 content/v2.0/account-management/multi-user/remove-user.md diff --git a/content/v2.0/account-management/multi-member/_index.md b/content/v2.0/account-management/multi-member/_index.md deleted file mode 100644 index 83f3d33da..000000000 --- a/content/v2.0/account-management/multi-member/_index.md +++ /dev/null @@ -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 >}} diff --git a/content/v2.0/account-management/multi-member/invite-member.md b/content/v2.0/account-management/multi-member/invite-member.md deleted file mode 100644 index 7f1bf84d4..000000000 --- a/content/v2.0/account-management/multi-member/invite-member.md +++ /dev/null @@ -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 %}} diff --git a/content/v2.0/account-management/multi-member/remove-memberr.md b/content/v2.0/account-management/multi-member/remove-memberr.md deleted file mode 100644 index 614bebe14..000000000 --- a/content/v2.0/account-management/multi-member/remove-memberr.md +++ /dev/null @@ -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. diff --git a/content/v2.0/account-management/multi-user/_index.md b/content/v2.0/account-management/multi-user/_index.md new file mode 100644 index 000000000..365fe95fe --- /dev/null +++ b/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 >}} diff --git a/content/v2.0/account-management/multi-user/invite-user.md b/content/v2.0/account-management/multi-user/invite-user.md new file mode 100644 index 000000000..b3cfb526f --- /dev/null +++ b/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 %}} diff --git a/content/v2.0/account-management/multi-user/remove-user.md b/content/v2.0/account-management/multi-user/remove-user.md new file mode 100644 index 000000000..f00d2e034 --- /dev/null +++ b/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.