[Improvement]: Fix JFrog OIDC docs #20604 (#59399)

Author: am-stead

content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-azure.md

@@ -77,7 +77,6 @@ The [`azure/login`](https://github.com/Azure/login) action receives a JWT from t
 
 The following example exchanges an OIDC ID token with Azure to receive an access token, which can then be used to access cloud resources.
 
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 name: Run Azure Login with OIDC
@@ -93,9 +92,9 @@ jobs:
       - name: 'Az CLI login'
         uses: azure/login@8c334a195cbb38e46038007b304988d888bf676a
         with:
-          client-id: ${{ secrets.AZURE_CLIENT_ID }}
-          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
-          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
+          client-id: {% raw %}${{ secrets.AZURE_CLIENT_ID }}{% endraw %}
+          tenant-id: {% raw %}${{ secrets.AZURE_TENANT_ID }}{% endraw %}
+          subscription-id: {% raw %}${{ secrets.AZURE_SUBSCRIPTION_ID }}{% endraw %}
 
       - name: 'Run az commands'
         run: |

content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-google-cloud-platform.md

@@ -103,7 +103,7 @@ jobs:
     - id: 'gcloud'
       name: 'gcloud'
       run: |-
-        gcloud auth login --brief --cred-file="${{ steps.auth.outputs.credentials_file_path }}"
+        gcloud auth login --brief --cred-file="{% raw %}${{ steps.auth.outputs.credentials_file_path }}{% endraw %}"
         gcloud services list
 ```
 

content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-jfrog.md

@@ -69,7 +69,7 @@ jobs:
         id: setup-jfrog-cli
         uses: jfrog/setup-jfrog-cli@29fa5190a4123350e81e2a2e8d803b2a27fed15e
         with:
-          JF_URL: ${{ env.JF_URL }}
+          JF_URL: {% raw %}${{ env.JF_URL }}{% endraw %}
           oidc-provider-name: 'YOUR_PROVIDER_NAME'
           oidc-audience: 'YOUR_AUDIENCE' # This is optional
 
@@ -85,20 +85,16 @@ jobs:
 
 ### Using OIDC Credentials in other steps
 
-{% raw %}
-
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
       - name: Sign in to Artifactory Docker registry
         uses: docker/login-action@v3
         with:
-          registry: ${{ env.JF_URL }}
-          username: ${{ steps.setup-jfrog-cli.outputs.oidc-user }}
-          password: ${{ steps.setup-jfrog-cli.outputs.oidc-token }}
+          registry: {% raw %}${{ env.JF_URL }}{% endraw %}
+          username: {% raw %}${{ steps.setup-jfrog-cli.outputs.oidc-user }}{% endraw %}
+          password: {% raw %}${{ steps.setup-jfrog-cli.outputs.oidc-token }}{% endraw %}
 ```
 
-{% endraw %}
-
 ## Further reading
 
 * [OpenID Connect Integration](https://jfrog.com/help/r/jfrog-platform-administration-documentation/openid-connect-integration) in the JFrog documentation

content/actions/tutorials/build-and-test-code/ruby.md

@@ -187,8 +187,6 @@ The `setup-ruby` actions provides a method to automatically handle the caching o
 
 To enable caching, set the following.
 
-{% raw %}
-
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 steps:
@@ -197,8 +195,6 @@ steps:
     bundler-cache: true
 ```
 
-{% endraw %}
-
 This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by {% data variables.product.prodname_actions %} and re-downloaded for subsequent workflow runs. A hash of your `gemfile.lock` and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
 
 **Caching without setup-ruby**

content/actions/tutorials/build-and-test-code/swift.md

@@ -124,8 +124,6 @@ jobs:
 
 You can configure your job to use a single specific version of Swift, such as `5.3.3`.
 
-{% raw %}
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 steps:
@@ -136,8 +134,6 @@ steps:
     run: swift --version # Swift 5.3.3
 ```
 
-{% endraw %}
-
 ## Building and testing your code
 
 You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job: