Skip to content

Commit d455649

Browse files
Gerry-FordeGerry-Forde
authored
Merge branch 'release-1.6' into RHIDP-6544
2 parents 0cb57eb + 33e9204 commit d455649

File tree

58 files changed

+892
-561
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

58 files changed

+892
-561
lines changed

‎artifacts/attributes.adoc‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,12 @@
1010
:product: Red Hat Developer Hub
1111
:product-short: Developer Hub
1212
:product-very-short: RHDH
13-
:product-version: 1.5
14-
:product-bundle-version: 1.5.0
15-
:product-chart-version: 1.5.0
16-
:product-backstage-version: 1.35.0
13+
:product-local: Red Hat Developer Hub Local
14+
:product-local-very-short: RHDH Local
15+
:product-version: 1.6
16+
:product-bundle-version: 1.6.0
17+
:product-chart-version: 1.6.0
18+
:product-backstage-version: 1.36.1
1719
:product-custom-resource-type: Backstage
1820
:rhdeveloper-name: Red Hat Developer
1921
:rhel: Red Hat Enterprise Linux

‎assemblies/assembly-configuring-authorization-in-rhdh.adoc‎

Lines changed: 7 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,18 @@
11
[id='configuring-authorization-in-rhdh']
22
= Configuring authorization in {product}
33

4-
In link:{authorization-book-url}[{authentication-book-title}], you learnt how to authenticate users to {product}.
5-
{product-short} knowns who the users are.
4+
Administrators can authorize users to perform actions and define what users can do in {product-short}.
65

7-
In this book, learn how to authorize users to perform actions in {product-short}.
8-
Define what users can do in {product-short}.
6+
Role-based access control (RBAC) is a security concept that defines how to control access to resources in a system by specifying a mapping between users of the system and the actions that those users can perform on resources in the system.
7+
You can use RBAC to define roles with specific permissions and then assign the roles to users and groups.
98

10-
Role-Based Access Control (RBAC) is a security concept that controls access to resources in a system, and specifies a mapping between users of the system, and the actions they can perform on resources in the system.
11-
You define roles with specific permissions, and then assign the roles to users and groups.
9+
RBAC on {product-short} is built on top of the Permissions framework, which defines RBAC policies in code. Rather than defining policies in code, you can use the {product-short} RBAC feature to define policies in a declarative fashion by using a simple CSV based format. You can define the policies by using {product-short} web interface or REST API instead of editing the CSV directly.
1210

13-
RBAC on {product-short} is built on top of the Permissions framework, which defines RBAC policies in code.
14-
Rather than defining policies in code,
15-
the {product-short} RBAC feature allows you
16-
to define policies in a declarative fashion using a simple CSV based format.
17-
You can define the policies by using {product-short} web interface or REST API, rather than editing the CSV directly.
11+
An administrator can define authorizations in {product-short} by taking the following steps:
1812

19-
To define authorizations in {product-short}:
13+
. Enable the RBAC feature and give authorized users access to the feature.
2014

21-
. The {product-short} administrator enables and gives access to the RBAC feature.
22-
23-
. You define your roles and policies by combining the following methods:
15+
. Define roles and policies by combining the following methods:
2416

2517
* The {product-short} policy administrator uses the {product-short} web interface or REST API.
2618
* The {product-short} administrator edits the main {product-short} configuration file.
@@ -58,4 +50,3 @@ include::modules/authorization/con-user-stats-rhdh.adoc[leveloffset=+1]
5850

5951

6052
include::modules/authorization/proc-download-user-stats-rhdh.adoc[leveloffset=+2]
61-

‎assemblies/assembly-configuring-default-secret-pvc-mounts.adoc‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="assembly-configuring-default-secret-pvc-mounts_{context}"]
3+
= Configuring default mounts for Secrets and PVCs
4+
5+
You can configure Persistent Volume Claims (PVCs) and Secrets mount in your {product} deployment. Use annotations to define the custom mount paths and specify the containers to mount them to.
6+
7+
include::modules/configuring-external-databases/proc-configuring-mount-paths.adoc[leveloffset=+1]
8+
9+
include::modules/configuring-external-databases/proc-mounting-to-specific-containers.adoc[leveloffset=+1]

‎assemblies/assembly-customizing-segment-source.adoc‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="customizing-segment-source_{context}"]
3+
= Customizing Segment source
4+
5+
The `analytics-provider-segment` plugin sends the collected web analytics data to {company-name} by default. However, you can configure a new Segment source that receives web analytics data based on your needs. For configuration, you need a unique Segment write key that points to the Segment source.
6+
7+
[NOTE]
8+
====
9+
Create your own web analytics data collection notice for your application users.
10+
====
11+
12+
include::modules/analytics/proc-customizing-segment-source-using-the-operator.adoc[leveloffset=+1]
13+
14+
include::modules/analytics/proc-customizing-segment-source-using-helm-the-helm-chart.adoc[leveloffset=+1]
15+
16+
.Additional resources
17+
* To learn how to collect and analyze the same set of data, see link:{telemetry-data-collection-book-url}[{telemetry-data-collection-book-title}].

‎assemblies/assembly-disabling-telemetry-data-collection.adoc‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="disabling-telemetry-data-collection_{context}"]
3+
= Disabling telemetry data collection in {product-very-short}
4+
5+
To disable telemetry data collection, you must disable the `analytics-provider-segment` plugin either using the Helm Chart or the {product} Operator configuration.
6+
7+
As an administrator, you can disable the telemetry data collection feature based on your needs. For example, in an air-gapped environment, you can disable this feature to avoid needless outbound requests affecting the responsiveness of the {product-very-short} application. For more details, see the link:{telemetry-data-collection-book-url}#proc-disabling-telemetry-using-operator_title-telemetry[Disabling telemetry data collection in {product-very-short}] section.
8+
9+
include::modules/analytics/proc-disabling-telemetry-using-operator.adoc[leveloffset=+1]
10+
11+
include::modules/analytics/proc-disabling-telemetry-using-helm.adoc[leveloffset=+1]

‎modules/observe/ref-enabling-telemetry.adoc‎ renamed to ‎assemblies/assembly-enabling-telemetry-data-collection.adoc‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
1+
:_mod-docs-content-type: ASSEMBLY
12
[id="enabling-telemetry-data-collection_{context}"]
23
= Enabling telemetry data collection in {product-very-short}
34

45
The telemetry data collection feature is enabled by default. However, if you have disabled the feature and want to re-enable it, you must enable the `analytics-provider-segment` plugin either by using the Helm Chart or the {product} Operator configuration.
56

7+
include::modules/analytics/proc-enabling-telemetry-using-operator.adoc[leveloffset=+1]
8+
9+
include::modules/analytics/proc-enabling-telemetry-using-helm.adoc[leveloffset=+1]

‎assemblies/assembly-install-rhdh-eks-operator.adoc‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="assembly-install-rhdh-eks-operator"]
3+
= Installing {product-short} on {eks-short} with the Operator
4+
5+
The {product} Operator installation requires the Operator Lifecycle Manager (OLM) framework.
6+
7+
.Additional resources
8+
* For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.
9+
10+
include::modules/installation/proc-rhdh-deploy-eks-operator.adoc[leveloffset=+1]

‎assemblies/assembly-managing-labels-annotations-topology.adoc‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="assembly-managing-labels-annotations-topology"]
3+
= Managing labels and annotations for Topology plugins
4+
:context: assembly-managing-labels-annotations-topology
5+
6+
include::modules/dynamic-plugins/proc-linking-to-source-code-editor-or-source.adoc[leveloffset=+1]
7+
8+
include::modules/dynamic-plugins/proc-entity-annotation-or-label.adoc[leveloffset=+1]
9+
10+
include::modules/dynamic-plugins/proc-namespace-annotation.adoc[leveloffset=+1]
11+
12+
include::modules/dynamic-plugins/proc-label-selector-query-annotation.adoc[leveloffset=+1]
13+
14+
include::modules/dynamic-plugins/proc-icon-displayed-in-the-node.adoc[leveloffset=+1]
15+
16+
include::modules/dynamic-plugins/proc-app-grouping.adoc[leveloffset=+1]
17+
18+
include::modules/dynamic-plugins/proc-node-connector.adoc[leveloffset=+1]
19+
20+
For more information about the labels and annotations, see _Guidelines for labels and annotations for OpenShift applications_.

‎assemblies/assembly-rhdh-telemetry.adoc‎

Lines changed: 0 additions & 41 deletions
This file was deleted.

‎assemblies/assembly-techdocs-add-docs.adoc‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
:context: assembly-techdocs-add-docs
3+
[id="{context}"]
4+
= Adding documentation to TechDocs
5+
6+
After an administrator configures the TechDocs plugin, a developer can add documentation to TechDocs by importing it from a remote repository. Any authorized user or group can access the documentation that is imported into the TechDocs plugin.
7+
8+
include::modules/techdocs/proc-techdocs-add-docs-from-remote-repo.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)