Releases: salto-io/salto
Salto v0.1.27
What's New in Version 0.1.27
What's New
- Added version validation on workspace to warn when using an old workspace with a new CLI
- Improved help text for move-to and create commands
- Improvements to Salto core memory consumption
Salesforce adapter
- Added more references in CPQ instances
- Improved support for salesforce types with content (Certificate, ContentAsset, EclairGeoData, NetworkBranding, SiteDotCom)
Bug Fixes
Netsuite adapter
- Fixed issue in deploy when the directory already existed
- omit ZeroWidthSpace chars upon deploy
Salto v0.1.26
What's New in Version v0.1.26
Salesforce adapter
- Support MatchingRules.
- Added more references in CPQ configuration.
- Update CPQ configuration example.
- Added upsert logic for Custom Object Instances on Add based on saltoIDSettings in the dataManagement configuration. Deploying Instances between environments is now "safer". It will not create logically duplicate Instances when they are already created as side effect of other Adds or already exist in the target environment.
Netsuite adapter
- Expose default configuration values.
- Use newer SuiteCloud Development Framework version.
Visual Studio Code extension
- Support symbol search on fields.
Upgrading from v0.1.25
If you have an existing workspace with NetSuite service, you should create a new workspace and add NetSuite service to it. This will download the new SuiteCloud Development Framework version.
Once the service is added, you can remove the new workspace and continue to work on your old one.
The salto
commands that has to be done to create workspace with NetSuite service are:
salto init
salto service add netsuite --nologin
Salto v0.1.25
What's New in Version v0.1.25
What's New
- Multi-env command documentation updated
Salesforce adapter
- Additional dependencies from Tooling API
- Fetch internal IDs of metadata instances
- Validate custom object instance ID fields are queryable
Netsuite adapter
- Bump SDF version
Bug Fixes
- Fixed error on string attribute keys during parse
- Stop trying sending telemetry if the error is unrecoverable
- Remove list type mismatch validation warnings on annotations
- Fix Salto element move command not working without -e
Salto v0.1.24
What's New in Version v0.1.24
What's New
- Diff commands between environments
Salesforce adapter
- Support Custom Feed Filter
Bug Fixes
- Correctly hide fields added to existing elements
- Drop elements that cause merge errors on fetch
- Parser issue with the same element appears multiple times in the same file
Salto v0.1.23
What's New in Version v0.1.23
Salesforce adapter
- Add more references
- Support deploy on more types
- Allow the user to control the definition of each CustomObject's instances SaltoID in the configuration
Netsuite adapter
- Fetch dataset’s dependencies in a consistent order
Visual Studio Code extension
- Remove duplicate workspace parsing errors
Bug Fixes
- Fix pending changes that conflicted with fetch result upon list’s order changes
- Update workspace respects the force flag
- Parser issue with the same element appears multiple times in the same file
Upgrading to v0.1.23
Remove dataManagement
from /salto.config/adapters/salesforce.nacl (or replace it with the example in https://github.com/salto-io/salto/blob/master/packages/salesforce-adapter/example-cpq-config.md)
Salto v0.1.22
What's New in Version v0.1.22
Salesforce adapter
- Improve deploy performance for CustomObject Instances.
- Modify dataManagement config:
- Support regular expressions for includeObjects, excludeObjects and allowReferenceTo.
- Remove includeNamespaces list.
Netsuite adapter
- Update types definitions.
Visual Studio Code extension
- Don't display warnings if errors exist.
Bug Fixes
- Avoid printing values upon workspace validations to prevent too long output.
- Fix Salesforce deploy changes on SocialCustomerServiceSettings that occurred immediately after fetch.
Upgrading from v0.1.21
If you had an enabled dataManagement in Salesforce adapter configuration:
- For each "OLD_VALUE" value in includeNamespaces, add "^OLD_VALUE__.*" to includeObjects list.
- Remove the includeNamespaces key and its values from the dataManagement config file.
Salto v0.1.21
What's New in Version v0.1.21
What's New
- Improve Fetch and Deploy performance.
- Zip the state file to reduce its size.
Salesforce adapter
- Modify static-resources folder structure.
- Fetch AuraDefinitionBundles & LightningComponentBundles from Installed Packages.
- Modifications to default configuration.
- Add more reference expressions.
Netsuite adapter
- Resistence for listFiles failure due to insufficient permissions.
- Support non textual File Cabinet content.
Bug Fixes
- Fix Salesforce SocialCustomerService type definition to avoid identifying non-existing changes.
- Fix Netsuite Dataset type definition correctly to avoid type mismatch validation warnings.
Salto v0.1.20
What's New in Version v0.1.20
What's New
- Improve Fetch and Deploy performance.
- Support static files with non textual content.
Salesforce adapter
- Update the default CPQ data management configuration.
- Add more references to elements.
- Extract the content of Aura Definition Bundle and Lightning Component Bundle to static files.
- Support Static Resources.
Netsuite adapter
- Define Workflow type correctly to avoid type mismatch validation warnings.
- Support deploying instances that has dependencies.
- Suggest filePathRegexSkipList configuration change in case of failure when importing files.
- Control SDF concurrency using sdfConcurrencyLimit configuration value.
Bug Fixes
- Avoid changing the current env when --env is passed as a command-line argument.
- Append to log file instead of overwriting the existing content.
- Fixed errors when modifying an env specific file in the extension
Salto v0.1.19
What's New in Version v0.1.19
What's New
- Added a new
netsuite
adapter, - Improved first fetch duration.
- Added a new
restore
command. (See Documentation) - Added a new
--dry-run
flag for the deploy command. (See Documentation) - Removed the
preview
command. - Seperated the envs config from the
workspace.nacl
config file toenvs.nacl
. (See Upgrade note below)
Salesforce adapter
- Added the ability to fetch and deploy custom object's instances.
- Salesforce types will not be written to the NaCL files.
- Default skip list changes:
- Added profiles
- Removed territory types.
- Added the missing
operator
field toReportFilterItem
.
Bug Fixes
- Fixed salto fails when a validation error is created for a value with a circular reference.
Upgrading from v0.1.18
v0.1.19 modifies the workspace configuration. In order to upgrade an exsiting Salto workspace please do the following:
- Copy and delete the content of the
envs
key inside./salto.config/workspace.nacl
- Create a new file
./salto.config/envs.nacl
with the following content:
envs {
envs = <content copied and removed from workspace.nacl>
}
For example - if the current content of ./salto.config/workspace.nacl
is:
workspace {
uid = "0d85811c-c448-4a3d-acfb-XXXXXXX"
name = "example"
staleStateThresholdMinutes = undefined
envs = [
{
name = "env1"
services = [
"salesforce",
]
},
]
}
You should end up with the following two files:
./salto.config/workspace.nacl
workspace {
uid = "0d85811c-c448-4a3d-acfb-XXXXXXX"
name = "example"
staleStateThresholdMinutes = undefined
}
./salto.config/envs.nacl
envs {
envs = [
{
name = "env1"
services = [
"salesforce",
]
},
]
}
Salto v0.1.18
What's New in Version v0.1.18
What's New
- Added a new fetch command flag
--state-only
to fetch service changes to the state file without applying them the the NaCL file. - Added a new flag
-d
to the preview command to display a more detailed deploy plan. - Added the abilty to define regex based restriction and validations.
VScode extension
- Added goto defintion and goto references support for type level annotations
- Added support for VScode version 1.36
Salesforce adapter
- Added a configuration flag
hideTypesInNacls
to toggle the ability to store certain types in the state file and not in the NaCL files. - Added territory types to the default skip list.
Bug Fixes
- Fixed new elements are create in the NaCL files with an extra indentation level
- Fixed references inside an array are not indented when dumped in the NaCL files.
- Fixed the ability to deploy static file content for cached static files.
- Fixed comments are in NaCL files cause parsing errors.