Add Aviary org docs (#225)

Author: cd-work

docs/artifact_repositories/cargo.md

@@ -13,13 +13,13 @@ authentication. You can find out how to generate one in our
 In the following examples, all API keys will be represented as
 `<PHYLUM_API_KEY>`, so make sure to replace them with your generated key.
 
-Additionally, if the default [policy] is not sufficient, a group can be passed
-to evaluate all packages against the group's policy. To do this, just replace
-`<PHYLUM_GROUP>` with the desired group name. The supplied API key **must** have
-access to this group.
+Additionally, if the default policy is not sufficient, a group can be passed to
+evaluate all packages against the group's policy. To do this, just replace
+`<PHYLUM_ORG>` and `<PHYLUM_GROUP>` with the desired org and group name. The
+supplied API key **must** have access to this group.
 
-If Phylum's default [policy] is sufficient, you can remove all instances of
-`<PHYLUM_GROUP>`.
+If Phylum's default [policy] is sufficient, you can omit the username from the
+authentication details.
 
 [API Keys documentation]: ../knowledge_base/api-keys.md#generate-an-api-key
 [policy]: ../knowledge_base/policy.md
@@ -72,10 +72,10 @@ global-credential-providers = ["cargo:token"]
 Once the file-based `cargo:token` credential provider is configured, you can add
 your authentication details to the [`.cargo/credentials.toml` file].
 
-The Phylum group and API key first need to be converted to Base64:
+The Phylum org, group, and API key first need to be converted to Base64:
 
 ```text
-printf "<PHYLUM_GROUP>:<PHYLUM_API_KEY>" | base64
+printf "<PHYLUM_ORG>/<PHYLUM_GROUP>:<PHYLUM_API_KEY>" | base64
 ```
 
 > ⚠️ **WARNING** ⚠️

docs/artifact_repositories/maven.md

@@ -13,24 +13,24 @@ authentication. You can find out how to generate one in our
 In the following examples, all API keys will be represented as
 `<PHYLUM_API_KEY>`, so make sure to replace them with your generated key.
 
-Additionally, if the default [policy] is not sufficient, a group can be passed
-to evaluate all packages against the group's policy. To do this, just replace
-`<PHYLUM_GROUP>` with the desired group name. The supplied API key **must** have
-access to this group.
+Additionally, if the default policy is not sufficient, a group can be passed to
+evaluate all packages against the group's policy. To do this, just replace
+`<PHYLUM_ORG>` and `<PHYLUM_GROUP>` with the desired org and group name. The
+supplied API key **must** have access to this group.
 
-If Phylum's default [policy] is sufficient, you can remove all instances of
-`<PHYLUM_GROUP>`.
+If Phylum's default [policy] is sufficient, you can omit the username from the
+authentication details.
 
 [API Keys documentation]: ../knowledge_base/api-keys.md#generate-an-api-key
 [policy]: ../knowledge_base/policy.md
 
 ### `mvn`
 
 The Phylum authorization header expects a token in Base64, so you first need to
-convert your Phylum group and API key:
+convert your Phylum org, group, and API key:
 
 ```sh
-printf "<PHYLUM_GROUP>:<PHYLUM_API_KEY>" | base64
+printf "<PHYLUM_ORG>/<PHYLUM_GROUP>:<PHYLUM_API_KEY>" | base64
 ```
 
 > ⚠️ **WARNING** ⚠️

docs/artifact_repositories/npm.md

@@ -13,13 +13,13 @@ authentication. You can find out how to generate one in our
 In the following examples, all API keys will be represented as
 `<PHYLUM_API_KEY>`, so make sure to replace them with your generated key.
 
-Additionally, if the default [policy] is not sufficient, a group can be passed
-to evaluate all packages against the group's policy. To do this, just replace
-`<PHYLUM_GROUP>` with the desired group name. The supplied API key **must** have
-access to this group.
+Additionally, if the default policy is not sufficient, a group can be passed to
+evaluate all packages against the group's policy. To do this, just replace
+`<PHYLUM_ORG>` and `<PHYLUM_GROUP>` with the desired org and group name. The
+supplied API key **must** have access to this group.
 
-If Phylum's default [policy] is sufficient, you can remove all instances of
-`<PHYLUM_GROUP>`.
+If Phylum's default [policy] is sufficient, you can omit the username from the
+authentication details.
 
 [API Keys documentation]: ../knowledge_base/api-keys.md#generate-an-api-key
 [policy]: ../knowledge_base/policy.md
@@ -30,7 +30,7 @@ Custom NPM registries can be configured with `npm`:
 
 ```sh
 npm config set replace-registry-host never
-npm config set registry https://<PHYLUM_GROUP>:<PHYLUM_API_KEY>@npm.phylum.io/
+npm config set registry https://<PHYLUM_ORG>%2F<PHYLUM_GROUP>:<PHYLUM_API_KEY>@npm.phylum.io/
 ```
 
 > ⚠️ **WARNING** ⚠️

docs/artifact_repositories/pypi.md

@@ -15,11 +15,11 @@ In the following examples, all API keys will be represented as
 
 Additionally, if the default policy is not sufficient, a group can be passed to
 evaluate all packages against the group's policy. To do this, just replace
-`<PHYLUM_GROUP>` with the desired group name. The supplied API key **must** have
-access to this group.
+`<PHYLUM_ORG>` and `<PHYLUM_GROUP>` with the desired org and group name. The
+supplied API key **must** have access to this group.
 
-If Phylum's default [policy] is sufficient, you can remove all instances of
-`<PHYLUM_GROUP>`.
+If Phylum's default [policy] is sufficient, you can omit the username from the
+authentication details.
 
 [API Keys documentation]: ../knowledge_base/api-keys.md#generate-an-api-key
 [policy]: ../knowledge_base/policy.md
@@ -30,14 +30,14 @@ The easiest way to install a package using the Phylum PyPI registry is using
 `pip`'s `--index-url` option:
 
 ```sh
-pip install --index-url https://<PHYLUM_GROUP>:<PHYLUM_API_KEY>@pypi.phylum.io/simple/ <requirement specifier>
+pip install --index-url https://<PHYLUM_ORG>%2F<PHYLUM_GROUP>:<PHYLUM_API_KEY>@pypi.phylum.io/simple/ <requirement specifier>
 ```
 
 To make this permanent for all `pip` invocations, you can add it to the `pip`
 configuration:
 
 ```sh
-pip config set global.index-url https://<PHYLUM_GROUP>:<PHYLUM_API_KEY>@pypi.phylum.io/simple/
+pip config set global.index-url https://<PHYLUM_ORG>%2F<PHYLUM_GROUP>:<PHYLUM_API_KEY>@pypi.phylum.io/simple/
 ```
 
 > ⚠️ **WARNING** ⚠️
@@ -62,7 +62,7 @@ directory:
 
 ```sh
 poetry source add phylum https://pypi.phylum.io/simple/
-poetry config http-basic.phylum "<PHYLUM_GROUP>" "<PHYLUM_API_KEY>"
+poetry config http-basic.phylum "<PHYLUM_ORG>%2F<PHYLUM_GROUP>" "<PHYLUM_API_KEY>"
 ```
 
 > ⚠️ **WARNING** ⚠️

docs/artifact_repositories/rubygems.md

@@ -13,13 +13,13 @@ authentication. You can find out how to generate one in our
 In the following examples, all API keys will be represented as
 `<PHYLUM_API_KEY>`, so make sure to replace them with your generated key.
 
-Additionally, if the default [policy] is not sufficient, a group can be passed
-to evaluate all packages against the group's policy. To do this, just replace
-`<PHYLUM_GROUP>` with the desired group name. The supplied API key **must** have
-access to this group.
+Additionally, if the default policy is not sufficient, a group can be passed to
+evaluate all packages against the group's policy. To do this, just replace
+`<PHYLUM_ORG>` and `<PHYLUM_GROUP>` with the desired org and group name. The
+supplied API key **must** have access to this group.
 
-If Phylum's default [policy] is sufficient, you can remove all instances of
-`<PHYLUM_GROUP>`.
+If Phylum's default [policy] is sufficient, you can omit the username from the
+authentication details.
 
 [API Keys documentation]: ../knowledge_base/api-keys.md#generate-an-api-key
 [policy]: ../knowledge_base/policy.md
@@ -39,7 +39,7 @@ After setting up the mirror, you also need to provide Phylum's group and API key
 for authorization:
 
 ```sh
-bundle config set --global rubygems.phylum.io <PHYLUM_GROUP>:<PHYLUM_API_KEY>
+bundle config set --global rubygems.phylum.io <PHYLUM_ORG>%2F<PHYLUM_GROUP>:<PHYLUM_API_KEY>
 ```
 
 > ⚠️ **WARNING** ⚠️