\
- Note callout: Focuses on the storage cost implications of enabling the setting
- Caution callout: Focuses on the risk of making recovery points unusable when disabled
* use stub from #6151 to populate july updates
* Update content/influxdb3/cloud-dedicated/reference/release-notes/cloud-dedicated.md
---------
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
* add mcp server documentation for core, enterprise, and cloud-dedicated
* Apply suggestions from code review
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
* updated mcp server npm/docker package names, updated environment variables
* updated the mcp server instructions to be correct
---------
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
fixes Docker environment variable configuration and Docker Compose examples for InfluxDB 3 Enterprise, along with several documentation improvements. The changes primarily address incorrect environment variable names and missing volume mounts in Docker setup examples.
Corrects the environment variable from INFLUXDB3_LICENSE_EMAIL to INFLUXDB3_ENTERPRISE_LICENSE_EMAIL across Enterprise documentation
Adds missing volume mounts to Docker Compose examples for both Core and Enterprise configurations
The influxdata-archive.key is designed to have a good user experience
during key rotations, but in order to do that, we need to properly
verify the key file's fingerprint and not its sha256sum (since the
primary key's fingerprint won't change with key rotations, but the
sha256sum necessarily will).
Update documentation for this to establish best practice and prepare
users for the upcoming key rotation.
Adjust dockerfiles to use this methodology.
- Verified precision behavior in source code. Added auto-detection note for all APIs: Added a note
explaining that InfluxDB 3 uses timestamp magnitude to
auto-detect precision by default, and users can specify
precision to avoid ambiguity.
- Fix allowed precision values\
- Add examples
Fix `create token --admin` name in frontmatter
Improve schedule trigger docs with more detail:
1. Core API documentation
(/api-docs/influxdb3/core/v3/ref.yml):
- Added missing duration units (weeks, months, years)
- Added "Maximum interval: 1 year"
2. Enterprise API documentation
(/api-docs/influxdb3/enterprise/v3/ref.yml):
- Added missing duration units (weeks, months, years)
- Added "Maximum interval: 1 year"
3. CLI reference documentation
(/content/shared/influxdb3-cli/create/trigger.md):
- Added complete list of supported duration units
- Added "Maximum interval is 1 year" note
All documentation now consistently reflects:
- The complete set of supported duration units for
every triggers
- The 1-year maximum limit for interval-based
scheduling
- Clear examples showing the syntax
Fix `create token --admin` name in frontmatter
Improve schedule trigger docs with more detail:
1. Core API documentation
(/api-docs/influxdb3/core/v3/ref.yml):
- Added missing duration units (weeks, months, years)
- Added "Maximum interval: 1 year"
2. Enterprise API documentation
(/api-docs/influxdb3/enterprise/v3/ref.yml):
- Added missing duration units (weeks, months, years)
- Added "Maximum interval: 1 year"
3. CLI reference documentation
(/content/shared/influxdb3-cli/create/trigger.md):
- Added complete list of supported duration units
- Added "Maximum interval is 1 year" note
All documentation now consistently reflects:
- The complete set of supported duration units for
every triggers
- The 1-year maximum limit for interval-based
scheduling
- Clear examples showing the syntax
Scott Anderson
Jason Stirnaman
Jason Stirnaman
ritwika314
Scott Anderson
Jamie Strandboge
David Rusnak
David Rusnak