From 64a18f0b2e2c748cfc233411cd93d906b7693384 Mon Sep 17 00:00:00 2001 From: Bernard Kitchens Date: Fri, 13 Mar 2020 14:22:58 -0700 Subject: [PATCH] docs(teams): updated team docs to reflect new MFA workflow for npm team api --- docs/content/cli-commands/npm-team.md | 2 ++ lib/team.js | 8 ++++---- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/content/cli-commands/npm-team.md b/docs/content/cli-commands/npm-team.md index 9a63b10c26f32..0d5782f0e04b4 100644 --- a/docs/content/cli-commands/npm-team.md +++ b/docs/content/cli-commands/npm-team.md @@ -30,6 +30,8 @@ handle permissions for packages. Teams must always be fully qualified with the organization/scope they belong to when operating on them, separated by a colon (`:`). That is, if you have a `wombats` team in a `wisdom` organization, you must always refer to that team as `wisdom:wombats` in these commands. +If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp ]`. If you don't include this then you will be prompted. + * create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, learn more. * add / rm: diff --git a/lib/team.js b/lib/team.js index 2b56e3b14f95b..e24f733475a23 100644 --- a/lib/team.js +++ b/lib/team.js @@ -14,10 +14,10 @@ team.subcommands = ['create', 'destroy', 'add', 'rm', 'ls', 'edit'] team.usage = usage( 'team', - 'npm team create \n' + - 'npm team destroy \n' + - 'npm team add \n' + - 'npm team rm \n' + + 'npm team create [--otp ]\n' + + 'npm team destroy [--otp ]\n' + + 'npm team add [--otp ]\n' + + 'npm team rm [--otp ]\n' + 'npm team ls |\n' + 'npm team edit ' )