[arvados] updated: 2.7.0-656-g3485717566

[git repository hosting]

Summary of changes:
 doc/api/index.html.textile.liquid | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

       via  348571756698f34074a5448ceee4eb7590ca3cd7 (commit)
      from  72f74086108b60a46458895411dd9afdaae8f383 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 348571756698f34074a5448ceee4eb7590ca3cd7
Author: Brett Smith <brett.smith at curii.com>
Date:   Fri Sep 29 10:21:50 2023 -0400

    20932: Update API index for Workbench 2 default
    
    * Just call it "Workbench," not "Workbench 2" or "new Workbench."
    * Remove reference to Workbench 1 Advanced tab.
    
    Refs #20932.
    
    Arvados-DCO-1.1-Signed-off-by: Brett Smith <brett.smith at curii.com>

diff --git a/doc/api/index.html.textile.liquid b/doc/api/index.html.textile.liquid
index 3d69d02ea9..44ca265cd8 100644
--- a/doc/api/index.html.textile.liquid
+++ b/doc/api/index.html.textile.liquid
@@ -18,12 +18,8 @@ The API server publishes a machine-readable description of its endpoints and som
 
 h2. Exported configuration
 
-The Controller exposes a subset of the cluster's configuration and makes it available to clients in JSON format. This public config includes valuable information like several service's URLs, timeout settings, etc. and it is available at @/arvados/v1/config@, for example @https://{{ site.arvados_api_host }}/arvados/v1/config at . The new Workbench is one example of a client using this information, as it's a client-side application and doesn't have access to the cluster's config file.
+The Controller exposes a subset of the cluster's configuration and makes it available to clients in JSON format. This public config includes valuable information like several service's URLs, timeout settings, etc. and it is available at @/arvados/v1/config@, for example @https://{{ site.arvados_api_host }}/arvados/v1/config at . Workbench is one example of a client using this information, as it's a client-side application and doesn't have access to the cluster's config file.
 
 h2. Exported vocabulary definition
 
-When configured, the Controller also exports the "metadata vocabulary definition":{{site.baseurl}}/admin/metadata-vocabulary.html in JSON format. This functionality is useful for clients like Workbench2 and the Python SDK to provide "identifier to human-readable labels" translations facilities for reading and writing objects on the system. This is available at @/arvados/v1/vocabulary@, for example @https://{{ site.arvados_api_host }}/arvados/v1/vocabulary at .
-
-h2. Workbench examples
-
-Many Arvados Workbench pages, under the *Advanced* tab, provide examples of API and SDK use for accessing the current resource .
+When configured, the Controller also exports the "metadata vocabulary definition":{{site.baseurl}}/admin/metadata-vocabulary.html in JSON format. This functionality is useful for clients like Workbench and the Python SDK to translate between identifiers and human-readable labels when reading and writing objects on the system. This is available at @/arvados/v1/vocabulary@, for example @https://{{ site.arvados_api_host }}/arvados/v1/vocabulary at .

-----------------------------------------------------------------------


hooks/post-receive
--