35 lines
1.4 KiB
YAML
35 lines
1.4 KiB
YAML
# Notification data structure
|
|
#
|
|
# - id: unique ID for notification, cannot start with digit, no spaces, a-z and 0-9
|
|
# level: note or warn
|
|
# scope:
|
|
# - list of URL paths to show notification on, no scope shows everywhere
|
|
# title: Message title
|
|
# slug: (optional) Short notification summary
|
|
# message: |
|
|
# Markdown message content.
|
|
|
|
- id: future-of-flux
|
|
level: warn
|
|
scope:
|
|
- /flux/v0
|
|
- /influxdb/v1
|
|
- /influxdb/v2
|
|
- /influxdb/cloud/
|
|
title: The future of Flux
|
|
slug: |
|
|
Flux is going into maintenance mode. You can continue using it as you
|
|
currently are without any changes to your code.
|
|
message: |
|
|
Flux is going into maintenance mode and will not be supported in InfluxDB 3.0.
|
|
This was a decision based on the broad demand for SQL and the continued growth
|
|
and adoption of InfluxQL. We are continuing to support Flux for users in 1.x
|
|
and 2.x so you can continue using it with no changes to your code.
|
|
If you are interested in transitioning to InfluxDB 3.0 and want to
|
|
future-proof your code, we suggest using InfluxQL.
|
|
|
|
For information about the future of Flux, see the following:
|
|
|
|
- [The plan for InfluxDB 3.0 Open Source](https://influxdata.com/blog/the-plan-for-influxdb-3-0-open-source)
|
|
- [InfluxDB 3.0 benchmarks](https://influxdata.com/blog/influxdb-3-0-is-2.5x-45x-faster-compared-to-influxdb-open-source/)
|