@influxdata/influxdb3-mcp-server 1.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +194 -0
- package/Dockerfile +22 -0
- package/LICENSE +6 -0
- package/LICENSE-APACHE.txt +201 -0
- package/LICENSE-MIT.txt +25 -0
- package/README.md +318 -0
- package/build/config.js +85 -0
- package/build/helpers/enums/influx-product-types.enum.js +8 -0
- package/build/index.js +33 -0
- package/build/prompts/index.js +98 -0
- package/build/resources/index.js +223 -0
- package/build/server/index.js +104 -0
- package/build/services/base-connection.service.js +318 -0
- package/build/services/cloud-token-management.service.js +179 -0
- package/build/services/context-file.service.js +97 -0
- package/build/services/database-management.service.js +549 -0
- package/build/services/help.service.js +241 -0
- package/build/services/http-client.service.js +109 -0
- package/build/services/influxdb-master.service.js +117 -0
- package/build/services/query.service.js +499 -0
- package/build/services/serverless-schema-management.service.js +266 -0
- package/build/services/token-management.service.js +215 -0
- package/build/services/write.service.js +153 -0
- package/build/tools/categories/cloud-token.tools.js +321 -0
- package/build/tools/categories/database.tools.js +299 -0
- package/build/tools/categories/health.tools.js +75 -0
- package/build/tools/categories/help.tools.js +104 -0
- package/build/tools/categories/query.tools.js +180 -0
- package/build/tools/categories/schema.tools.js +308 -0
- package/build/tools/categories/token.tools.js +378 -0
- package/build/tools/categories/write.tools.js +104 -0
- package/build/tools/index.js +27 -0
- package/env.example +17 -0
- package/example-cloud-dedicated.mcp.json +15 -0
- package/example-cloud-serverless.mcp.json +13 -0
- package/example-clustered.mcp.json +14 -0
- package/example-docker.mcp.json +25 -0
- package/example-local.mcp.json +13 -0
- package/example-npx.mcp.json +13 -0
- package/package.json +78 -0
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,194 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to the official InfluxDB MCP Server will be documented in this file.
|
|
4
|
+
|
|
5
|
+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
|
+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
|
+
|
|
8
|
+
## [1.3.0] - 2026-05-18
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
|
|
12
|
+
- **E2E test suite**: Protocol compliance tests (vitest) that verify server startup, MCP handshake, tool/resource/prompt registration, and error handling — no InfluxDB required
|
|
13
|
+
- **Integration tests**: Live InfluxDB tests for `health_check`, `list_databases`, and `execute_query`, gated behind `INFLUX_TEST_ENABLED`
|
|
14
|
+
- **Error-path unit tests**: Tests with recorded error fixtures from live Core and Cloud Serverless instances covering JSON, plain-text, and `{code, message}` error formats
|
|
15
|
+
- **CI workflow**: GitHub Actions with protocol tests on every PR, integration tests against InfluxDB 3 Core via Docker, and Cloud Serverless integration tests via GitHub environment secrets
|
|
16
|
+
- **Docker test infrastructure**: `docker-compose.test.yml` for local Core testing with preconfigured admin token
|
|
17
|
+
- **Version consistency CI check**: Verifies `package.json`, `config.ts`, and `CHANGELOG.md` versions match on every PR
|
|
18
|
+
- **CLAUDE.md**: Architecture overview and codebase conventions for Claude Code
|
|
19
|
+
- **Claude Code skills**: Build/run workflow for Core/Enterprise and testing workflow
|
|
20
|
+
|
|
21
|
+
### Fixed
|
|
22
|
+
|
|
23
|
+
- Server-level error catch now sets `isError: true`, consistent with handler-level error responses
|
|
24
|
+
- Plain-text error responses from InfluxDB Core (HTTP 500) are now surfaced in all 4 services instead of falling through to generic "Internal Server Error"
|
|
25
|
+
- Query error handler now checks `data.message` for Cloud Serverless `{code, message}` JSON error format, matching the other 3 services
|
|
26
|
+
|
|
27
|
+
### Changed
|
|
28
|
+
|
|
29
|
+
- Minimum Node.js version raised to v20.11 (Node 18 is EOL; vitest 4.x and `import.meta.dirname` require v20.11+)
|
|
30
|
+
- `@modelcontextprotocol/sdk` updated from `^1.12.1` to `1.27.1`
|
|
31
|
+
- `@influxdata/influxdb3-client` updated from `^1.1.0` to `1.4.0`
|
|
32
|
+
- All dependencies updated to latest within semver ranges
|
|
33
|
+
- Version aligned across `package.json`, `config.ts`, and `CHANGELOG.md` (previously divergent)
|
|
34
|
+
- npm package renamed from `influxdb-mcp-server` to `@influxdata/influxdb3-mcp-server`
|
|
35
|
+
- Scoped package configured for public publish (`publishConfig.access: "public"`)
|
|
36
|
+
- All dependencies pinned to exact versions (no caret ranges)
|
|
37
|
+
|
|
38
|
+
## [1.2.0] - 2025-11-05
|
|
39
|
+
|
|
40
|
+
### Added
|
|
41
|
+
|
|
42
|
+
- **InfluxDB Cloud Serverless Support**: Complete support for InfluxDB Cloud Serverless instances
|
|
43
|
+
|
|
44
|
+
- Full database management with Cloud Serverless specific parameters: `description`, `retentionPeriod`
|
|
45
|
+
- Support for bucket operations (Cloud Serverless databases are called "buckets")
|
|
46
|
+
- Enhanced `create_database` and `update_database` tools with Cloud Serverless configuration
|
|
47
|
+
- Bucket renaming support via `newName` parameter in `update_database`
|
|
48
|
+
- Specialized response parsing for Cloud Serverless `_fields` array format
|
|
49
|
+
- Schema exploration via `information_schema` queries compatible with Cloud Serverless
|
|
50
|
+
- New configuration files: `env.cloud-serverless.example` and `example-cloud-serverless.mcp.json`
|
|
51
|
+
|
|
52
|
+
- **Custom Context System**: Optional user-provided database context and documentation
|
|
53
|
+
|
|
54
|
+
- New `ContextFileService` for flexible context file discovery
|
|
55
|
+
- `context-file` MCP resource exposing custom documentation via `influx://context`
|
|
56
|
+
- `load-context` MCP prompt for one-click context loading
|
|
57
|
+
- `load_database_context` tool for agents to access user-provided context
|
|
58
|
+
- Support for multiple context file formats: JSON, Markdown, and plain text
|
|
59
|
+
- Flexible file placement: `/context/` folder or files with "context" in name
|
|
60
|
+
|
|
61
|
+
### Enhanced
|
|
62
|
+
|
|
63
|
+
- **Query Operations**:
|
|
64
|
+
|
|
65
|
+
- Universal CAST requirements documentation for both Cloud Dedicated and Cloud Serverless
|
|
66
|
+
- Enhanced query tools with product-specific guidance for aggregation functions
|
|
67
|
+
- Proper handling of Cloud Serverless response format with `_fields` arrays
|
|
68
|
+
- Updated query examples with correct CAST syntax for v3 cloud products
|
|
69
|
+
|
|
70
|
+
- **Database Management**:
|
|
71
|
+
|
|
72
|
+
- Cloud Serverless bucket lifecycle management (create, update, delete, list)
|
|
73
|
+
- Retention period enforcement awareness and error handling
|
|
74
|
+
- Product-specific parameter validation and configuration
|
|
75
|
+
- Enhanced database listing with Cloud Serverless metadata
|
|
76
|
+
|
|
77
|
+
- **Write Operations**:
|
|
78
|
+
|
|
79
|
+
- Retention period violation handling for cloud instances
|
|
80
|
+
- Improved error messages for timestamp-related write failures
|
|
81
|
+
- Enhanced line protocol validation and troubleshooting guidance
|
|
82
|
+
|
|
83
|
+
- **Help System**:
|
|
84
|
+
- Updated help content with Cloud Serverless specific requirements
|
|
85
|
+
- Added retention period error guidance for cloud instances
|
|
86
|
+
- Enhanced query documentation with CAST requirements for cloud products
|
|
87
|
+
- Context system usage documentation
|
|
88
|
+
|
|
89
|
+
### Technical Improvements
|
|
90
|
+
|
|
91
|
+
- Product type detection and response parsing for Cloud Serverless
|
|
92
|
+
- Enhanced error handling for retention period violations
|
|
93
|
+
- Improved type safety for multi-product database operations
|
|
94
|
+
- Context file service with flexible discovery patterns
|
|
95
|
+
- Better separation of cloud-specific vs universal query requirements
|
|
96
|
+
|
|
97
|
+
## [1.1.0] - 2025-06-23
|
|
98
|
+
|
|
99
|
+
### Added
|
|
100
|
+
|
|
101
|
+
- **InfluxDB Cloud Dedicated Support**: Complete support for InfluxDB Cloud Dedicated clusters
|
|
102
|
+
|
|
103
|
+
- New `update_database` tool for Cloud Dedicated database configuration management
|
|
104
|
+
- Support for Cloud Dedicated specific parameters: `maxTables`, `maxColumnsPerTable`, `retentionPeriod`
|
|
105
|
+
- Enhanced `create_database` tool with optional Cloud Dedicated configuration parameters
|
|
106
|
+
- Dual token support: separate database tokens and management tokens for Cloud Dedicated
|
|
107
|
+
- New cloud token management tools: `cloud_list_database_tokens`, `cloud_get_database_token`, `cloud_create_database_token`, `cloud_update_database_token`, `cloud_delete_database_token`
|
|
108
|
+
- New configuration files: `env.cloud-dedicated.example` and `example-cloud-dedicated.mcp.json`
|
|
109
|
+
|
|
110
|
+
- **Enhanced Validation System**: Comprehensive operation validation based on product type and configuration
|
|
111
|
+
|
|
112
|
+
- All operations now validate required capabilities before execution
|
|
113
|
+
- Product type-specific operation restrictions (e.g., token management only for Core/Enterprise)
|
|
114
|
+
- Configuration validation ensures proper credentials for each operation type
|
|
115
|
+
- Descriptive error messages for invalid operations and missing configuration
|
|
116
|
+
|
|
117
|
+
- **Improved Documentation**:
|
|
118
|
+
- Updated README with Cloud Dedicated configuration examples
|
|
119
|
+
- New environment variable examples for all supported InfluxDB types
|
|
120
|
+
- Tool availability matrix showing Core/Enterprise vs Cloud Dedicated compatibility
|
|
121
|
+
- Enhanced help content with Cloud Dedicated specific guidance
|
|
122
|
+
|
|
123
|
+
### Enhanced
|
|
124
|
+
|
|
125
|
+
- **Database Management**:
|
|
126
|
+
|
|
127
|
+
- `create_database` tool now supports Cloud Dedicated configuration parameters
|
|
128
|
+
- `list_databases` returns Cloud Dedicated specific database metadata
|
|
129
|
+
- All database operations now properly validate management capabilities
|
|
130
|
+
|
|
131
|
+
- **Connection Management**:
|
|
132
|
+
|
|
133
|
+
- Improved health checking with flexible endpoint assessment
|
|
134
|
+
- Better connection status reporting for different InfluxDB product types
|
|
135
|
+
- Enhanced error handling for Cloud Dedicated authentication scenarios
|
|
136
|
+
|
|
137
|
+
- **Configuration Flexibility**:
|
|
138
|
+
- Support for multiple token types (database vs management)
|
|
139
|
+
- Intelligent host selection for data operations vs management operations
|
|
140
|
+
- Proper credential validation for each operation type
|
|
141
|
+
|
|
142
|
+
### Technical Improvements
|
|
143
|
+
|
|
144
|
+
- Refactored BaseConnectionService with comprehensive validation methods
|
|
145
|
+
- Enhanced HTTP client with better error handling for management API calls
|
|
146
|
+
- Improved type safety and error messages throughout the codebase
|
|
147
|
+
- Better separation of data plane and control plane operations
|
|
148
|
+
- Refactored MCP tools into modular category-based files for improved maintainability and organization
|
|
149
|
+
|
|
150
|
+
## [1.0.0] - 2025-06-13
|
|
151
|
+
|
|
152
|
+
### Added
|
|
153
|
+
|
|
154
|
+
- Initial release of official InfluxDB MCP Server
|
|
155
|
+
- Full support for InfluxDB v3 Core and Enterprise
|
|
156
|
+
- Complete set of MCP tools for database operations:
|
|
157
|
+
- Database management (create, list, delete)
|
|
158
|
+
- Data querying with SQL support
|
|
159
|
+
- Line protocol data writing
|
|
160
|
+
- Token management (admin and resource tokens)
|
|
161
|
+
- Health checking and diagnostics
|
|
162
|
+
- MCP resources for real-time status monitoring:
|
|
163
|
+
- `influx-status`: Comprehensive health and connection status
|
|
164
|
+
- `influx-config`: Current configuration details
|
|
165
|
+
- MCP prompts for common operations:
|
|
166
|
+
- `list-databases`: Generate database listing prompts
|
|
167
|
+
- `check-health`: Generate health check prompts
|
|
168
|
+
- `query-recent-data`: Generate recent data query prompts
|
|
169
|
+
- Comprehensive help system with detailed guidance
|
|
170
|
+
- Support for multiple deployment methods:
|
|
171
|
+
- Local development
|
|
172
|
+
- NPM package
|
|
173
|
+
- Docker container
|
|
174
|
+
- Example MCP configuration files for easy setup
|
|
175
|
+
- Complete TypeScript implementation with proper error handling
|
|
176
|
+
- Modular architecture with specialized services
|
|
177
|
+
|
|
178
|
+
### Features
|
|
179
|
+
|
|
180
|
+
- **Query Service**: Simplified response processing for InfluxDB v3 arrays
|
|
181
|
+
- **Write Service**: Direct line protocol support with comprehensive examples
|
|
182
|
+
- **Token Management**: Full CRUD operations for admin and resource tokens
|
|
183
|
+
- **Database Management**: Complete database lifecycle management
|
|
184
|
+
- **Help Service**: In-memory help content for optimal LLM performance
|
|
185
|
+
- **Health Monitoring**: Real-time status checking with detailed diagnostics
|
|
186
|
+
|
|
187
|
+
### Technical Details
|
|
188
|
+
|
|
189
|
+
- Built with @modelcontextprotocol/sdk v1.12.1
|
|
190
|
+
- Uses @influxdata/influxdb3-client for InfluxDB connectivity
|
|
191
|
+
- TypeScript with strict mode enabled
|
|
192
|
+
- ESM module support
|
|
193
|
+
- Comprehensive error handling and validation
|
|
194
|
+
- Supports stdio transport
|
package/Dockerfile
ADDED
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
FROM node:20-alpine
|
|
2
|
+
WORKDIR /app
|
|
3
|
+
|
|
4
|
+
# Copy package files and install dependencies
|
|
5
|
+
COPY package*.json ./
|
|
6
|
+
RUN npm ci
|
|
7
|
+
|
|
8
|
+
# Copy source and build
|
|
9
|
+
COPY src/ ./src/
|
|
10
|
+
COPY tsconfig.json ./
|
|
11
|
+
RUN npm run build
|
|
12
|
+
RUN chmod +x ./build/index.js
|
|
13
|
+
|
|
14
|
+
# Create non-root user
|
|
15
|
+
RUN addgroup -g 1001 -S nodejs && \
|
|
16
|
+
adduser -S mcp -u 1001 -G nodejs
|
|
17
|
+
|
|
18
|
+
# Change ownership and switch to non-root user
|
|
19
|
+
RUN chown -R mcp:nodejs /app
|
|
20
|
+
USER mcp
|
|
21
|
+
|
|
22
|
+
CMD ["node", "build/index.js"]
|
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/LICENSE-MIT.txt
ADDED
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
Copyright (c) 2020 InfluxData
|
|
2
|
+
|
|
3
|
+
Permission is hereby granted, free of charge, to any
|
|
4
|
+
person obtaining a copy of this software and associated
|
|
5
|
+
documentation files (the "Software"), to deal in the
|
|
6
|
+
Software without restriction, including without
|
|
7
|
+
limitation the rights to use, copy, modify, merge,
|
|
8
|
+
publish, distribute, sublicense, and/or sell copies of
|
|
9
|
+
the Software, and to permit persons to whom the Software
|
|
10
|
+
is furnished to do so, subject to the following
|
|
11
|
+
conditions:
|
|
12
|
+
|
|
13
|
+
The above copyright notice and this permission notice
|
|
14
|
+
shall be included in all copies or substantial portions
|
|
15
|
+
of the Software.
|
|
16
|
+
|
|
17
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
|
|
18
|
+
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
|
|
19
|
+
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
|
|
20
|
+
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
|
|
21
|
+
SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
|
|
22
|
+
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
|
|
23
|
+
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
|
|
24
|
+
IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
|
|
25
|
+
DEALINGS IN THE SOFTWARE.
|