Skip to content

Commit ed4b615

Browse files
authored
chore: clean up EOL release references (#5100)
Refs: RHIDP-13595 Signed-off-by: Jon Koops <jonkoops@gmail.com>
1 parent 41e0cdc commit ed4b615

8 files changed

Lines changed: 41 additions & 304 deletions

File tree

.github/workflows/pr-1.8.yaml

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

docs/auth.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -269,6 +269,4 @@ auth:
269269

270270
External authentication providers can be loaded using the dynamic plugins mechanism. Typically this will require a backend plugin to provide the authentication provider API implementation and callback handling, and a frontend plugin to connect this API to important parts of the UI in the form of a [custom SignInPage](dynamic-plugins/frontend-plugin-wiring.md#use-a-custom-signinpage-component) and [provider settings](dynamic-plugins/frontend-plugin-wiring.md#adding-custom-authentication-provider-settings) entries for the user settings page.
271271

272-
The existing Developer Hub authentication module will need to be disabled by setting an [environment variable](dynamic-plugins/override-core-services.md#overriding-the-provided-authentication-module), `ENABLE_AUTH_PROVIDER_MODULE_OVERRIDE` to `true` for the Developer Hub backend.
273-
274-
Some examples of composing dynamic plugins to provide an authentication solution are available in the [dynamic plugins examples](dynamic-plugins/examples.md).
272+
The existing Developer Hub authentication module will need to be disabled by setting an [environment variable](dynamic-plugins/override-core-services.md#overriding-the-provided-authentication-module), `ENABLE_AUTH_PROVIDER_MODULE_OVERRIDE` to `true` for the Developer Hub backend.

docs/dynamic-plugins/examples.md

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

docs/dynamic-plugins/index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,6 @@ More details about publishing dynamic plugins is in the [Packaging Dynamic Plugi
3333

3434
[Wrapping a third-party backend plugin to add dynamic plugin support](wrapping-plugins.md)
3535

36-
[Examples](examples.md)
37-
3836
## Installing external Backstage plugins into RHDH
3937

4038
1. Get the source code of the plugin.

docs/dynamic-plugins/installing-plugins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
To install a dynamic plugin, you need to add the plugin definition to the `dynamic-plugins.yaml` file.
44

55
The placement of `dynamic-plugins.yaml` depends on the deployment method.
6-
For more information, see [Installing Dynamic Plugins with the Red Hat Developer Hub Operator](https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.7/html/installing_and_viewing_plugins_in_red_hat_developer_hub/rhdh-installing-rhdh-plugins_title-plugins-rhdh-about#proc-config-dynamic-plugins-rhdh-operator_rhdh-installing-rhdh-plugins) or [Installing Dynamic Plugins Using the Helm Chart](https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.7/html/installing_and_viewing_plugins_in_red_hat_developer_hub/rhdh-installing-rhdh-plugins_title-plugins-rhdh-about#con-install-dynamic-plugin-helm_rhdh-installing-rhdh-plugins).
6+
For more information, see [Installing Dynamic Plugins with the Red Hat Developer Hub Operator](https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.10/html/installing_and_viewing_plugins_in_red_hat_developer_hub/install-dynamic-plugins-in-rhdh_installing-and-viewing-plugins-in-rhdh) or [Installing Dynamic Plugins Using the Helm Chart](https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.10/html/installing_and_viewing_plugins_in_red_hat_developer_hub/install-dynamic-plugins-in-rhdh_installing-and-viewing-plugins-in-rhdh).
77

88
Plugins are defined in the `plugins` array in the `dynamic-plugins.yaml` file. Each plugin is defined as an object with the following properties:
99

docs/e2e-tests/examples.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,7 @@ Some tests use a global page variable `let page: Page;`. This is used to avoid r
1111

1212
Examples:
1313

14-
* https://github.com/redhat-developer/rhdh/blob/release-1.5/e2e-tests/playwright/e2e/google-signin-happy-path.spec.ts
15-
* https://github.com/redhat-developer/rhdh/blob/release-1.5/e2e-tests/playwright/e2e/guest-signin-happy-path.spec.ts
14+
* [guest-signin-happy-path.spec.ts](../../e2e-tests/playwright/e2e/guest-signin-happy-path.spec.ts)
1615

1716
## Types of tests
1817

docs/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -230,8 +230,8 @@ spec:
230230
```
231231

232232
See these docs for more info:
233-
* https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.8/html-single/configuring_dynamic_plugins/index#installing-ansible-plug-ins-for-red-hat-developer-hub or
234-
* https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.8/html/configuring_red_hat_developer_hub/configuring-the-deployment
233+
* https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.10/html-single/configuring_dynamic_plugins/index#installing-ansible-plugins-for-rhdh_configuring-dynamic-plugins or
234+
* https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.10/html/configuring_red_hat_developer_hub/configure-rhdh-deployment-when-using-the-operator_configuring-rhdh
235235

236236

237237
### Customizing Telemetry Destination

0 commit comments

Comments
 (0)