@canopy-io/node 0.4.0 → 0.6.0

package/dist/index.js

@@ -550,29 +550,19 @@ var Identities = class {
       { body: input }
     );
   }
+  /**
+   * Takes the identity out of this key's Environment: its membership here is
+   * deactivated and its role assignments here are dropped. The identity and
+   * its access to other Environments are untouched. Deactivating an identity
+   * everywhere is an Account-level action, not available to an
+   * Environment-scoped key.
+   */
   delete(id) {
     return this.client.request(
       "DELETE",
       `/api/v1/identities/${encodeURIComponent(id)}`
     );
   }
-  /**
-   * Deactivation is the reversible counterpart to `delete` — sessions are
-   * revoked and sign-in refused, but the identity and its assignments survive.
-   * Prefer it for offboarding you may need to undo.
-   */
-  deactivate(id) {
-    return this.client.request(
-      "POST",
-      `/api/v1/identities/${encodeURIComponent(id)}/deactivate`
-    );
-  }
-  activate(id) {
-    return this.client.request(
-      "POST",
-      `/api/v1/identities/${encodeURIComponent(id)}/activate`
-    );
-  }
   /**
    * Every role this identity holds, and where — across all pages.
    *
@@ -634,7 +624,7 @@ var Identities = class {
    * Ends every session the identity holds, so the next refresh on any device
    * fails and the person signs in again. Access tokens already issued keep
    * working until their short lifetime runs out. For a suspected compromise;
-   * `deactivate` also refuses the next sign-in.
+   * `delete` also takes the identity out of this Environment.
    */
   revokeSessions(id) {
     return this.client.request(
@@ -1210,7 +1200,9 @@ var LocalAuthorizer = class {
    * With no argument, everything goes: grants and the hierarchy tree. Not
    * needed in normal operation, where entries expire on their own; useful in
    * tests and after a change whose reach you cannot name (a role's
-   * permissions edited, a node moved).
+   * permissions edited, a role deactivated or reactivated, a node moved). A
+   * deactivated role grants nothing to anyone holding it, so until the cache
+   * is cleared or expires, its holders keep being allowed locally.
    *
    * Multi-instance honesty: an invalidation reaches THIS process only. A
    * webhook lands on one instance behind a load balancer; the others serve