* manually replce all shared relrefs
* relref replace - previous grafana versions
* update test
* prettier
(cherry picked from commit 2cb999c4f3)
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
Co-authored-by: Robby Milo <robbymilo@fastmail.com>
This commit is contained in:
Jack Baldry
co-authored by
Robby Milo
Robby Milo
parent
d4703cc677
commit
8980faf989
@@ -25,7 +25,7 @@ For our purposes, a breaking change is any change that requires users or operato
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
|
||||
To learn what's available in a Grafana release, refer to the [What's new ]({{< relref "../whatsnew/" >}}) page for each version. For the steps we recommend when you upgrade, check out the [Upgrade guide]({{< relref "../upgrade-guide/" >}}) for each version.
|
||||
To learn what's available in a Grafana release, refer to the [What's new ](../whatsnew/) page for each version. For the steps we recommend when you upgrade, check out the [Upgrade guide](../upgrade-guide/) for each version.
|
||||
|
||||
{{% /admonition %}}
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ For each change, the provided information:
|
||||
- Guides you in how to mitigate for the change or migrate
|
||||
- Provides more learning resources
|
||||
|
||||
For release highlights and deprecations, refer to our [v10.0 What’s new]({{< relref "../whatsnew/whats-new-in-v10-0/" >}}). For the specific steps we recommend when you upgrade to v10.0, check out our [Upgrade guide]({{< relref "../upgrade-guide/upgrade-v10.0/index.md" >}}).
|
||||
For release highlights and deprecations, refer to our [v10.0 What’s new](../../whatsnew/whats-new-in-v10-0/). For the specific steps we recommend when you upgrade to v10.0, check out our [Upgrade guide](../../upgrade-guide/upgrade-v10.0/).
|
||||
|
||||
<!--
|
||||
## Feature
|
||||
@@ -47,13 +47,13 @@ You must use relative references when linking to docs within the Grafana repo. P
|
||||
|
||||
#### You are affected if:
|
||||
|
||||
You create a new Grafana Cloud stack and intend to use any panel or data source plugins written using the Angular.js JavaScript framework. See the [list of Angular plugins]({{< relref "../developers/angular_deprecation/angular-plugins/" >}}).
|
||||
You create a new Grafana Cloud stack and intend to use any panel or data source plugins written using the Angular.js JavaScript framework. See the [list of Angular plugins](../../developers/angular_deprecation/angular-plugins/).
|
||||
|
||||
#### Background
|
||||
|
||||
AngularJS is an old frontend framework that stopped active development many years ago. Because of that, it's a security risk. AngularJS also requires **unsafe-eval** in the [CSP (Content Security Policy)](https://developer.mozilla.org/en/Security/CSP) settings, which also reduces the security level of how javascript is executed in the browser.
|
||||
|
||||
Angular plugin support in Grafana is deprecated, meaning it will be removed in a future release. There are still some community and private plugins built using Angular. Starting with v9.0, Grafana has a server configuration option, called [angular_support_enabled]({{< relref "../setup-grafana/configure-grafana/#angular_support_enabled" >}}), that controls whether Angular plugin support is available.
|
||||
Angular plugin support in Grafana is deprecated, meaning it will be removed in a future release. There are still some community and private plugins built using Angular. Starting with v9.0, Grafana has a server configuration option, called [angular_support_enabled](../../setup-grafana/configure-grafana/#angular_support_enabled), that controls whether Angular plugin support is available.
|
||||
|
||||
#### Change in Grafana v10
|
||||
|
||||
@@ -61,13 +61,13 @@ Angular is disabled by default for all new Grafana Cloud stacks. Existing stacks
|
||||
|
||||
#### How to mitigate
|
||||
|
||||
If you're using Angular plugins in Grafana, try an alternative panel or data source that doesn't use Angular. This list of detected [Angular plugins]({{< relref "../developers/angular_deprecation/angular-plugins/" >}}) offers alternatives where they exist.
|
||||
If you're using Angular plugins in Grafana, try an alternative panel or data source that doesn't use Angular. This list of detected [Angular plugins](../../developers/angular_deprecation/angular-plugins/) offers alternatives where they exist.
|
||||
|
||||
If you're a developer maintaining a plugin that uses Angular, we recommend you refactor or rewrite its frontend using React.js instead. The team at Grafana is ready to help and provide tools and guidance; you can reach us in [Slack](https://grafana.slack.com/archives/C3HJV5PNE) or on our [Forum](https://community.grafana.com/c/plugin-development/30).
|
||||
|
||||
#### Learn more
|
||||
|
||||
- [Angular Support Deprecation documentation]({{< relref "../developers/angular_deprecation/" >}})
|
||||
- [Angular Support Deprecation documentation](../../developers/angular_deprecation/)
|
||||
|
||||
### Grafana legacy alerting is deprecated and no longer accepts internal or external contributions
|
||||
|
||||
@@ -95,15 +95,15 @@ In Grafana v8.5, we introduced [service accounts](https://grafana.com/blog/2022/
|
||||
|
||||
This is a "breaking" change because if users are used to seeing and interacting with API keys, they won't see that page in navigation anymore and will need to navigate to the **Service accounts** page instead. However, your existing API tokens will remain fully functional and migrated to service accounts, so no automation will break. If you roll back to a previous version of Grafana, your API keys will remain intact.
|
||||
|
||||
Grafana's [HTTP API endpoints for generating and managing API Keys]({{< relref "../developers/http_api/auth/#create-api-token" >}}) remain functional, but we recommend you begin using the [Service account HTTP API]({{< relref "../developers/http_api/serviceaccount/" >}}) to generate and manage machine authentication instead.
|
||||
Grafana's [HTTP API endpoints for generating and managing API Keys](../../developers/http_api/auth/#create-api-token) remain functional, but we recommend you begin using the [Service account HTTP API](../../developers/http_api/serviceaccount/) to generate and manage machine authentication instead.
|
||||
|
||||
#### Migration path
|
||||
|
||||
While upgrading to Grafana v10, you don't need to take any action; your API keys will be automatically migrated. To test or perform the migration from API keys to service accounts before upgrading to Grafana v10, follow our [migration documentation]({{< relref "../administration/api-keys/#migrate-api-keys-to-grafana-service-account" >}}").
|
||||
While upgrading to Grafana v10, you don't need to take any action; your API keys will be automatically migrated. To test or perform the migration from API keys to service accounts before upgrading to Grafana v10, follow our [migration documentation](../../administration/api-keys/#migrate-api-keys-to-grafana-service-account").
|
||||
|
||||
#### Learn more
|
||||
|
||||
- [Documentation on migrating from API keys to service accounts]({{< relref "../administration/api-keys/" >}})
|
||||
- [Documentation on migrating from API keys to service accounts](../../administration/api-keys/)
|
||||
|
||||
- [Blog post announcement with a video demo including how to migrate](https://grafana.com/blog/2022/08/24/new-in-grafana-9.1-service-accounts-are-now-ga/)
|
||||
|
||||
@@ -193,7 +193,7 @@ We strongly recommend not doing this in case you are using Azure AD as an identi
|
||||
#### Learn more
|
||||
|
||||
- [CVE-2023-3128 Advisory](https://grafana.com/security/security-advisories/cve-2023-3128/)
|
||||
- [Enable email lookup]({{< relref "../setup-grafana/configure-security/configure-authentication/" >}})
|
||||
- [Enable email lookup](../../setup-grafana/configure-security/configure-authentication/)
|
||||
|
||||
### The "Alias" field in the CloudWatch data source is removed
|
||||
|
||||
@@ -211,7 +211,7 @@ Open and save each dashboard that uses the Alias field. Alias is migrated to Lab
|
||||
|
||||
#### Learn more
|
||||
|
||||
- [Grafana CloudWatch documentation about the change]({{< relref "../datasources/aws-cloudwatch/query-editor/#label" >}})
|
||||
- [Grafana CloudWatch documentation about the change](../../datasources/aws-cloudwatch/query-editor/#label)
|
||||
|
||||
### Athena data source plugin must be updated to version >=2.9.3
|
||||
|
||||
|
||||
Reference in New Issue
Block a user