All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Don't include json files in the package
- Added default export for the SDK
- Added azure/core-utils as an official dependency
- Added "main" field back to package.json
- Changed type of projects to be "module" to support EcmaScript modules. It shouldn't affect the usage of the SDK, if it does please open an issue.
- Types are now properly exported using "export type"
- CloudInfo is now exported
- Server timeout was with accuracy of tenth of a second.
- Updated default endpoint urls
- Updated dependencies to fix security vulnerabilities
- Take
process.argv[1]
as an app identifier instead ofprocess.title
- More strict header escaping, limit the length to 100 characters per field
- Version number fix
- [BREAKING] - Minimal node version is now 18
- [BREAKING] - The default converters for DateTime and TimeSpan will now return null if the value is null or an empty string. This is to align with the behavior of the service.
- [BREAKING] - IngestClient returns
Promise<IngestionResult>
instead ofPromise<QueueSendMessageResponse>
- Added condition on file extension for binary file compression
- Support table status reporting like explained here https://learn.microsoft.com/en-us/azure/data-explorer/kusto/api/netfx/kusto-ingest-client-status
- When working with storage resources, use success/failure statistics and retry mechanism to improve ingestion stability
- process.env can be undefined
- Headers are now escaped better
- Bump @azure/identity to 3.3.2
- Fix nx on CI build
- Support new playfab domain
- Fix browser support for proxy clusters (with no metadata)
- Avoid node headers in browser (Accept-Encoding, Connection)
- Remove dependency on crypto browserify
- sample app for browser auth and run from react vite
- Export from index.ts more classes that are exposed to user
- Streaming from blob url is now supported (in ManagedStreamingIngest too)
- Some internal types exposed as they are retuned to the user.
- Remove streamify from browser flow
- Default tenant of user prompt was nullified if options were given
- Streaming from blob url is now supported (in ManagedStreamingIngest too)
- More robust handling of errors in queued ingestion (resource manager improvements)
- Fixed exports using the wrong types
IgnoreFirstRecord
ingestion option is now supported- Edge case in getting the username on azure functions environments is now handled by @Apokalypt
- ConnectionStringBuilder now accepts certificate path
- ConnectionStringBuilder now accepts a TokenCredential
- Fixed parsing of certain commands
- Remove authorization header from errors
- Escape non-ascii headers to align with the service
- Internal devops improvements
- Fixed issue with metadata endpoint in browsers by @sagivf
- [BREAKING] - the minimal version for NodeJS is now 16
- [BREAKING] - removed moment.js from project and fixed timespan parsing:
- By default, Timespan will now be parsed into a number of milliseconds by default, matching Date substraction
- By default, Datetime fields will now be parsed into a native Date object
- To change the default, use KustoResultTable.timeSpanParser and KustoResultTable.dateTimeParser
- Browser compatible package
- The SDK now supports being run in a browser
- See README.md for details
- Added Security.MD
- Overall bugs fixes
- Use azure identity instead of Msal for authentication
- moment.js
- Upgrade MSAL dependency
- Fix lockfile error
- Fix vulnerability - jsonwebtoken (again)
- Fix vulnerability - jsonwebtoken
- Add trident endpoint by @AsafMah in #227
- Fixed #221 - include missing file
- [Breaking] Trusted endpoints - by default kusto will only connect to trusted endpoints
- Closeable clients, you can now free resources when you are done with a client
- Added Ignorefirstrecord ingestion property
- Quick start improvements
- Bump parse-url from 7.0.2 to 8.1.0
- Fixed bug with using the moment library that caused ingestion resources not to refresh.
- Version 3.4.0 introduced a bug that caused the wrong client id to be sent in Managed Identity scenarios. This version fixes it, and the old version is deprecated.