You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/observe/scorecards/proc-authenticating-and-managing-scorecard-plugins.adoc
+1-25Lines changed: 1 addition & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,28 +23,4 @@ See {authorization-book-link}#ref-rbac-permission-policies_title-authorization[P
23
23
... To enable read access for the Scorecard plugin, add a policy with the following details and click *Next*:
24
24
**** *Permission*: `scorecard.metric.read`
25
25
**** *Action*: `read`
26
-
**** *Effect*: `allow`
27
-
28
-
. Provide users access to specific metrics by their identifiers by using a conditional policy to restrict access, for example, only to the GitHub Open PRs metric (`github.open_prs`) using any of the following ways:
29
-
** {audit-log-book-link}#managing-authorizations-by-using-the-web-ui[Using the Web UI].
30
-
** defining the conditional policies in an `rbac-conditional-policies.yaml` file as shown in the following code:
31
-
+
32
-
[source,yaml]
33
-
----
34
-
result: CONDITIONAL
35
-
roleEntityRef: "role:default/scorecard-viewer"
36
-
pluginId: scorecard
37
-
resourceType: scorecard-metric
38
-
permissionMapping:
39
-
- read
40
-
conditions:
41
-
rule: HAS_METRIC_ID
42
-
resourceType: scorecard-metric
43
-
params:
44
-
metricIds: [_<your_metric_id>_]
45
-
----
46
-
+
47
-
where:
48
-
`metricIds`:: Enter the metric ID you want to give access to a user. For example: `github.open_prs`.
49
-
50
-
This policy would allow users to read only the GitHub Open PRs metric, while restricting access to other available metrics.
Copy file name to clipboardExpand all lines: modules/observe/scorecards/proc-configuring-jira-scorecards-in-rhdh-instance.adoc
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,9 @@ The following Jira versions are supported:
14
14
* You must have administrator privileges for Jira and {product-very-short}.
15
15
* You have installed your {product-very-short} instance.
16
16
* You have installed the Scorecard images.
17
-
* You must have added a custom {product-very-short} application configuration.
17
+
* You must have {configuring-book-link}[added a custom {product-very-short} application configuration] and have enough permissions to change it.
18
18
19
-
---
20
-
== Procedure
19
+
.Procedure
21
20
22
21
. Create a Jira configuration token using one of the following methods, depending on your Jira product:
23
22
** Jira Cloud: https://id.atlassian.com/manage-profile/security/api-tokens[Create a personal token]. You must then create a `Base64-encoded` string using the following plain text format: `your-atlassian-email:your-jira-api-token`.
** Jira datacenter: Create and use a Personal Access Token (PAT) in your Jira datacenter account. For more information, see the https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html[Atlassian] documentation.
30
29
31
30
. Configure the Jira Scorecard plugin in your `{product-very-short} dynamic-plugins-config.yaml` using either a direct setup or a proxy setup.
32
-
.. Use a direct setup (Recommended for simpler environments): Add the following code to your `{product-very-short} dynamic-plugins-config.yaml`:
31
+
.. Use a direct setup: Add the following code to your `{product-very-short} dynamic-plugins-config.yaml`:
33
32
+
34
33
[source,yaml]
35
34
----
@@ -43,11 +42,12 @@ plugins:
43
42
product: datacenter # Change to 'cloud' if using Jira Cloud
44
43
----
45
44
where:
45
+
46
46
`baseUrl`:: Enter the Jira URL.
47
47
`token`:: Enter the Jira token (Base64 string for Cloud, PAT for Data Center).
48
48
`product`:: Enter the supported product: `cloud` or `datacenter`.
49
49
50
-
.. Use a proxy setup (Recommended for complex network environments): In your `{product-very-short} dynamic-plugins-config.yaml`, add the following code:
50
+
.. Use a proxy setup: In your `{product-very-short} dynamic-plugins-config.yaml`, add the following code:
51
51
+
52
52
[source,yaml]
53
53
----
@@ -60,7 +60,7 @@ plugins:
60
60
product: datacenter # Change to 'cloud' if using Jira Cloud
61
61
----
62
62
63
-
.. In your `{product-very-short} app-config.yaml` file, add the following proxy settings:
63
+
... In your `{product-very-short} app-config.yaml` file, add the following proxy settings:
64
64
+
65
65
[source,yaml]
66
66
----
@@ -75,6 +75,7 @@ proxy:
75
75
Authorization: ${JIRA_TOKEN} # Must be configured in your environment
76
76
----
77
77
where:
78
+
78
79
`Authorization`:: Set any of the following header value:
79
80
* For *Cloud*: `Basic YourCreatedAboveToken`
80
81
* For *Data Center*: `Bearer YourJiraToken`
@@ -102,6 +103,7 @@ spec:
102
103
providesApis: [example-grpc-api]
103
104
----
104
105
where:
106
+
105
107
`jira/project-key`:: Required: Enter the Jira project key.
106
108
`jira/component`:: Optional: Enter the Jira component name.
107
109
`jira/label`:: Optional: Enter the Jira label.
@@ -140,6 +142,7 @@ scorecard:
140
142
customFilter: priority in ("Critical", "Blocker")
141
143
----
142
144
where:
145
+
143
146
`mandatoryFilter`:: Optional: Replaces the default filter (`type = Bug and resolution = Unresolved`).
144
147
`customFilter`:: Optional: Specifies a global custom filter. The entity annotation `jira/custom-filter` overrides this value.
0 commit comments