Merge branch 'main' into repo-sync

Author: aurbiztondo-splunk

gdi/opentelemetry/collector-linux/install-linux-manual.rst

@@ -109,7 +109,7 @@ To install the Collector for Linux using a RPM package, set up the package repos
          cat <<EOH > /etc/yum.repos.d/splunk-otel-collector.repo
          [splunk-otel-collector]
          name=Splunk OpenTelemetry Collector Repository
-         baseurl=https://splunk.jfrog.io/splunk/otel-collector-rpm/release/\$basearch
+         baseurl=https://splunk.jfrog.io/splunk/otel-collector-rpm/release/$basearch
          gpgcheck=1
          gpgkey=https://splunk.jfrog.io/splunk/otel-collector-rpm/splunk-B3CD4420.pub
          enabled=1

splunkplatform/centralized-rbac.rst

@@ -84,6 +84,8 @@ To set up centralized user and role management, follow these steps:
     
               acs observability enable-capabilities
 
+    .. note:: It could take around 30 minutes for the new roles ``o11y_*`` to be available on the :guilabel:`Roles` page of Splunk Cloud. 
+
 3. Give all users who should have access to Splunk Observability Cloud the ``o11y_access`` role.
 
 4. Log in to Splunk Cloud Platform as an administrator and go to :guilabel:`Settings` then :guilabel:`Users and Authentication` then :guilabel:`Roles`. Assign Splunk Observability Cloud roles to users. The following Splunk Observability Cloud roles (with ``o11y_*`` prefix) are now visible in Splunk Cloud role management page:
@@ -110,8 +112,6 @@ To set up centralized user and role management, follow these steps:
     
       acs observability enable-centralized-rbac --o11y-access-token <access-token>
 
-.. note:: It takes around 30 minutes for a new role to be available on the :guilabel:`Roles` page. 
-
 How centralized user and role management works
 =================================================================================================