Skip to content

Salto v0.3.61
Compare
Choose a tag to compare
@saltoio saltoio released this 28 Jul 13:10
· 389 commits to main since this release
v0.3.61
62e2725
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Salto Version 0.3.61

New features and bug fixes

General

  • With the introduction of Turbocache, when you wish to build, test or lint a specific package, use the --filter argument, e.g.:
    yarn build --filter @salto-io/zendesk-adapter
    yarn test --filter @salto-io/netsuite-adapter
    yarn lint --filter @salto-io/salesforce-adapter

  • with this PR, we now support turbocache for both local tests and CircleCI.
    if you need to test a specific package, do (for example):
    yarn test --filter @salto-io/zendesk-adapter
    before the turbocache run, we will check if any source files have been modified in any of the dependencies of the package you are testing (or the entire project, if you run all tests).

VS-Code Extension

  • Support for meta types syntax.

Core

  • allowEmpty param is removed from transformElement. Alternatively, you may use allowEmptyArrays and allowEmptyObjects.
  • Fixed a bug parsing template static files with string interpolations.
  • Improved the handling of attribute values in getElementHiddenParts.
  • Fixing a bug that occurs when trying to apply a change which modifies an entire base type.
  • add filterFunc to applyDetailedChanges.
  • Change the API of createDiffChanges to receive an object param, and add it compareOptions, that are used in the elements comparison.

NetSuite adapter

  • fix fixElements of form fields that reference objects with appid

Jira adapter

  • keep post functions order in DC
  • Fixed a bug that caused errors in deployment when an issue layout had a missing parent reference
  • Fixed a bug that caused a change validator to fail a deploy operation

Salesforce adapter

  • Added pre & post deploy actions that guide users to disable their billing triggers for CPQ Billing Deployments.
  • Improved caching of listMetadataObjects: Same type won't be listed twice even when the requests are created concurrently.
  • Fixed a bug where deploy of LightningWebComponent failed on Attribute name "default" associated with an element type "property" must be followed by the ' = ' character.
  • Renamed the internal and hidden CustomObject and CustomMetadata types to _CustomObject and _CustomMetadata.
  • Renamed the internal and hidden CustomObject and CustomMetadata types to _CustomObject and _CustomMetadata.
  • Improved the dependencies between CPQ Rules and their conditions to avoid deploy issues due to missing reference.
  • Adds meta types to Salesforce types.
  • Excluding MutingPermissionSets and PermissionSetGroups by default for new accounts.
    -Aligning MutingPermissionSet instances support with PermissionSets.
  • Add references for QuickAction fieldOverrides.
  • The adapter will use API 61.0.
    Salesforce Types folder will be hidden by default.
    Improved references between CPQ Custom Rules and their conditions.

Zendesk adapter

  • Users can now authenticate to Zendesk with username and API Token

Okta_adapter:

  • Bug fix for deployment of priority of MultifactorEnrollmentPolicyRule
  • Fix bug in pagination for User type
  • Active Application instances can now be removed and do not require manual deactivation first.
  • Improve fetch time when including group memberships

Jamf adapter

  • support mac_application fetch and deploy
  • fix deploying references of site and category
  • Support deployment of scripts list on policy instance

Microsoft Entra:

  • Expand user-facing errors to include more informative messages when requests fail.

Expected changes to existing workspaces

Jamf adapter

  • support mac_application fetch and deploy
  • fix deploying references of site and category
  • Support deployment of scripts list on policy instance

Jira adapter

  • for DC users the order of post functions in workflow will change
  • prevent deploying portal groups with a non-unique name field

Salesforce adapter

  • Nearly all types will get meta types when the optional feature is enabled. This will lead to a change on the whole type which will remove the annotations definitions.
  • Existing MutingPermissionSet instances will have their structure changed.
  • Existing QuickAction instances may have changes from strings to References.
  • Existing workspaces will have major changes to their existing nacls.
Assets 6
Loading