diff --git a/.github/workflows/push-docs.yaml b/.github/workflows/push-docs.yaml index e3fc45c56f1..bacc176f521 100644 --- a/.github/workflows/push-docs.yaml +++ b/.github/workflows/push-docs.yaml @@ -25,6 +25,8 @@ jobs: copy-docs: runs-on: ubuntu-latest + outputs: + minor: ${{ steps.version-variables.outputs.minor }} steps: - name: Get LTS branch version id: lts-version @@ -162,16 +164,17 @@ jobs: slack-notification: runs-on: ubuntu-latest - needs: - - copy-docs + if: ${{ always() }} + needs: copy-docs steps: - name: Notify on workflow success if: | needs.copy-docs.result == 'success' env: SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }} + VERSION: ${{needs.copy-docs.outputs.minor}} run: | - MESSAGE="✅ *Success:* Automated copy of reference docs for ${{ steps.version-variables.outputs.minor }} was successful. " + MESSAGE="✅ *Success:* Automated copy of reference docs for ${VERSION} was successful. " curl \ -d "text=$MESSAGE" \ @@ -185,7 +188,7 @@ jobs: SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }} run: | JOB_URL=https://github.com/solo-io/gloo/actions/runs/${GITHUB_RUN_ID} - MESSAGE="❌ *Failure:* Automated copy of reference docs for ${{ steps.version-variables.outputs.minor }} failed. <${JOB_URL}|Review the workflow failure>" + MESSAGE="❌ *Failure:* Automated copy of reference docs for ${VERSION} failed. <${JOB_URL}|Review the workflow failure>" curl \ -d "text=$MESSAGE" \ diff --git a/changelog/v1.18.0-rc2/docs-deprecation.yaml b/changelog/v1.18.0-rc2/docs-deprecation.yaml new file mode 100644 index 00000000000..f4e433df4e8 --- /dev/null +++ b/changelog/v1.18.0-rc2/docs-deprecation.yaml @@ -0,0 +1,11 @@ +changelog: + - type: NON_USER_FACING + issueLink: https://github.com/solo-io/solo-projects/issues/7118 + resolvesIssue: true + description: >- + Add deprecation notice for GraphQL in 1.18+. + - type: NON_USER_FACING + issueLink: https://github.com/solo-io/solo-projects/issues/6960 + resolvesIssue: true + description: >- + Add deprecation notice for Plugin Auth in 1.18+. \ No newline at end of file diff --git a/docs/content/guides/graphql/_index.md b/docs/content/guides/graphql/_index.md index 085355fa8ed..b1e181a37cb 100644 --- a/docs/content/guides/graphql/_index.md +++ b/docs/content/guides/graphql/_index.md @@ -7,8 +7,9 @@ description: Enable GraphQL resolution. Set up API gateway and GraphQL server functionality for your apps in the same process by using Gloo Gateway. {{% notice warning %}} -This feature is deprecated in Gloo Gateway 1.18 and will be removed in a future release +This feature is deprecated in Gloo Gateway 1.18 and will be removed in a future release. {{% /notice %}} + {{% notice note %}} This feature is available only in Gloo Gateway Enterprise. {{% /notice %}} diff --git a/docs/content/guides/graphql/getting_started/_index.md b/docs/content/guides/graphql/getting_started/_index.md index aa8b4ece5b3..08e392691dc 100644 --- a/docs/content/guides/graphql/getting_started/_index.md +++ b/docs/content/guides/graphql/getting_started/_index.md @@ -6,8 +6,12 @@ description: Get started with enabling GraphQL in Gloo Gateway and resolving Gra Set up API gateway and GraphQL server functionality for your apps in the same process by using Gloo Gateway. +{{% notice warning %}} +This feature is deprecated in Gloo Gateway 1.18 and will be removed in a future release. +{{% /notice %}} + {{% notice note %}} -This feature is available only in Gloo Gateway Enterprise. Remote execution is supported only in versions 1.14.0 and later. +This feature is available only in Gloo Gateway Enterprise. {{% /notice %}} {{% children description="true" %}} \ No newline at end of file diff --git a/docs/content/guides/graphql/getting_started/setup.md b/docs/content/guides/graphql/getting_started/setup.md index 38037d78092..4015f0d7fe8 100644 --- a/docs/content/guides/graphql/getting_started/setup.md +++ b/docs/content/guides/graphql/getting_started/setup.md @@ -6,8 +6,12 @@ description: Install GraphQL in Gloo Gateway and enable API spec discovery for u Set up API gateway and GraphQL server functionality for your apps in the same process by using Gloo Gateway. +{{% notice warning %}} +This feature is deprecated in Gloo Gateway 1.18 and will be removed in a future release. +{{% /notice %}} + {{% notice note %}} -This feature is available only in Gloo Gateway Enterprise. Remote execution is supported only in versions 1.14.0 and later. +This feature is available only in Gloo Gateway Enterprise. {{% /notice %}} ## Step 1: Install GraphQL in Gloo Gateway diff --git a/docs/content/guides/security/auth/extauth/plugin_auth/_index.md b/docs/content/guides/security/auth/extauth/plugin_auth/_index.md index 74f0abadaf6..3245b2552c1 100644 --- a/docs/content/guides/security/auth/extauth/plugin_auth/_index.md +++ b/docs/content/guides/security/auth/extauth/plugin_auth/_index.md @@ -4,8 +4,8 @@ weight: 90 description: Extend Gloo Gateway's built-in auth server with custom Go plugins --- -{{% notice note %}} -This feature was introduced with **Gloo Gateway Enterprise**, release 0.18.11. If you are using an earlier version, this tutorial will not work. +{{% notice warning %}} +This feature is deprecated in Gloo Gateway 1.18 and will be removed in a future release. Consider using the [Passthrough Auth]({{< versioned_link_path fromRoot="/guides/security/auth/extauth/passthrough_auth/" >}}) feature instead. {{% /notice %}} We have seen that one way of implementing custom authentication logic is by [providing your own auth server]({{< versioned_link_path fromRoot="/guides/security/auth/custom_auth" >}}). While this approach gives you great freedom, it also comes at a cost: diff --git a/docs/content/operations/upgrading/faq.md b/docs/content/operations/upgrading/faq.md index f6e129aae78..d5da5f3b49a 100644 --- a/docs/content/operations/upgrading/faq.md +++ b/docs/content/operations/upgrading/faq.md @@ -99,10 +99,12 @@ The following lists consist of the changes that were initially introduced with t * **Apply JWT policy at the route-level**: Now, you can apply JWT policies to specific routes by configuring the `jwtProvidersStaged` settings in the route option. Previously, JWT policies applied at the gateway level and were configured in only the VirtualHost option. With this new feature, you can apply JWT policies at both the route and gateway level. For more information and example steps, see [Route-level JWT policy]({{< versioned_link_path fromRoot="/security/auth/jwt/route-jwt-policy/" >}}). -