Releases: enterspeedhq/enterspeed-cli
Releases · enterspeedhq/enterspeed-cli
3.0.1
3.0.0
Breaking
- Added support for folders.
The folder structure you have in the Enterspeed app is now reflected on your local disk when using the CLI.
Likewise, if you moved a schema to a folder on your local disk and call asave
orimport
command the folder structure is updated in the app.
With the introduction of folders, the staticpartials
folder is removed and the schema type is now part of the file name ([schemaAlias].[schemaType].[format]).
If you are already working with schemas on disk, you should clear theschemas
folder and run a newimport
command to get the new folder and file structure.
2.0.2
Fixed
- Fixed null reference exception if the local folder does not contains a
schemas
folder
2.0.1
Fixed
- Fixed description of default value for format (default is JavaScript) for
schema create
command
2.0.0
Added
- Added support for JavaScript schemas
Fixed
- Made environment required for list-deployed command as it always has been, we just threw an internal exception before
Breaking changes
- The JavaScript format is new the default format when creating schemas through the CLI
- To make it easier for you we have aligned naming convention so that commands are singular (
views
has been renamed toview
to be consitent with the other commands) - To make it easier for you we have aligned naming convention for all options to be kebab-case instead of a mix of camelCase and kebab-case
1.6.0
Added
- New command to list deployed schemas for an environment 'list-deployed'
Fixed
- Avoiding deployments of schemas that are already deployed on the environment
1.5.0
Added
- Added support for partial schemas (require new partial schemas enable on tenant)
1.4.0
Added
- Updated CLI to use new release endpoint to deploy schemas more effectively instead of one schema at a time
- Added telemetry on CLI version
1.3.0
Added
- Added source entity ingest command
- Added source entity delete command
1.2.0
Added
- Added support for destinations
Changed
- Change order of route placement to match schemas created in the app