chore: use the attribute instead of hardcoding the link for DPDY file in 1.8 (#2062)

* chore: use the attribute instead of hardcoding the link for DPDY file in 1.8

Signed-off-by: Nick Boldt <nboldt@redhat.com>

* echo the branch we're using as the source of the ccutil script so we can see why we're using main instead of release-1.y

Signed-off-by: Nick Boldt <nboldt@redhat.com>

* Apply suggestion from @nickboldt

---------

Signed-off-by: Nick Boldt <nboldt@redhat.com>

Author: nickboldt

.github/workflows/pr.yml

@@ -33,7 +33,7 @@ concurrency:
   group: ${{ github.workflow }}-${{ github.event.number || github.event.pull_request.head.ref }}
   cancel-in-progress: true
 
-env: 
+env:
   GH_TEAM: rhdh
   GH_ORGANIZATION: redhat-developer
 jobs:
@@ -47,7 +47,7 @@ jobs:
         uses: actions/create-github-app-token@29824e69f54612133e76f7eaac726eef6c875baf # v2.2.1
         with:
           app-id: ${{ secrets.RHDH_GITHUB_APP_ID }}
-          private-key: ${{ secrets.RHDH_GITHUB_APP_PRIVATE_KEY }} 
+          private-key: ${{ secrets.RHDH_GITHUB_APP_PRIVATE_KEY }}
       - name: Check team membership
         uses: redhat-developer/rhdh/.github/actions/check-author@main
         id: check-team-membership
@@ -104,13 +104,13 @@ jobs:
         run: |
           # update
           sudo apt-get update -y || true
-          # install 
+          # install
           sudo apt-get -y -q install podman && podman --version
           echo "GIT_BRANCH=${GITHUB_HEAD_REF:-${GITHUB_REF#refs/heads/}}" >> $GITHUB_ENV
 
       - name: Build guides and indexes
         run: |
-          echo "Building PR ${{ github.event.pull_request.number }}"
+          echo "Building PR ${{ github.event.pull_request.number }} using scripts from ${{ github.event.pull_request.base.ref }} branch"
           cp trusted-scripts/build/scripts/build-ccutil.sh pr-content/build/scripts/build-ccutil.sh
           cd pr-content
           build/scripts/build-ccutil.sh -b "pr-${{ github.event.number }}"
@@ -140,7 +140,7 @@ jobs:
           cd pr-content
           gh repo set-default "${ORG_REPO}"
           # for a given PR, check for existing comments from rhdh-bot; select the last one (if more than one)
-          if [[ $(gh api "repos/${ORG_REPO}/issues/${PR_NUM}/comments" -q 'map(select(.user.login=="rhdh-bot"))|last|.id') ]]; then 
+          if [[ $(gh api "repos/${ORG_REPO}/issues/${PR_NUM}/comments" -q 'map(select(.user.login=="rhdh-bot"))|last|.id') ]]; then
             # edit that comment:
             gh pr comment ${PR_NUM} -R "${ORG_REPO}" --edit-last --body "Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-${PR_NUM}/ @ $(date "+%x %X")"
           else

modules/dynamic-plugins/proc-enable-plugins-rhdh-container-image.adoc

@@ -8,15 +8,15 @@ In the {product-very-short} container image, a set of dynamic plugins is preload
 You can enable and configure the plugins in the {product-very-short} container image, including how to manage the default configuration, set necessary environment variables, and ensure the proper functionality of the plugins within your application.
 
 .Prerequisites
-* You have access to the link:https://raw.githubusercontent.com/redhat-developer/rhdh/refs/heads/release-1.8/dynamic-plugins.default.yaml[`dynamic-plugins.default.yaml`] file, which lists all preloaded plugins and their default configuration.
+* You have access to the link:{dynamic-plugins-default-yaml-link}[`dynamic-plugins.default.yaml`] file, which lists all preloaded plugins and their default configuration.
 * You have deployed the {product-very-short} application, and have access to the logs of the `install-dynamic-plugins` init container.
 * You have the necessary permissions to modify plugin configurations and access the application environment.
 * You have identified and set the required environment variables referenced by the plugin's default configuration. These environment variables must be defined in the Helm Chart or Operator configuration.
 
 .Procedure
 . Start your {product-very-short} application and access the logs of the `install-dynamic-plugins` init container within the {product-very-short} pod.
 . Identify the {dynamic-plugins-reference-book-link}#red-hat-supported-plugins[Red Hat supported plugins] that are disabled by default.
-. Copy the package configuration from the link:https://raw.githubusercontent.com/redhat-developer/rhdh/refs/heads/release-1.8/dynamic-plugins.default.yaml[`dynamic-plugins.default.yaml`] file.
+. Copy the package configuration from the link:{dynamic-plugins-default-yaml-link}[`dynamic-plugins.default.yaml`] file.
 . Open the plugin configuration file and locate the plugin entry you want to enable.
 +
 The location of the plugin configuration file varies based on the deployment method. For more details, see {installing-and-viewing-plugins-book-link}[{installing-and-viewing-plugins-book-title}].