Tags: salto-io/salto
Tags
Bump to version 0.5.2 (#7336) # Salto Version 0.5.2 ## New features and bug fixes ### Core - Fixed issue with parsing multiline template expressions that would lead to unintended pending changes - Fixed issue where merge errors would persist even if the offending element was removed - Fixed a bug where non-primitive fields were hidden from NaCl files if all of their inner fields were hidden - Breaking API change: The `FetchResult` type changed its `configChanges` parameter type from `Plan` to `Change[]` - return static file with content when there are common and env source - Fixed a bug where non-primitive fields were hidden from NaCl files if all of their inner fields were hidden - Store elements with the correct nacl file path for adapter format commands - Removed export of `closeRemoteMapsOfLocation`. use `workspace.close()` / `remoteMapCreator.close()` instead ### Adapter_API - Added getOptionsType, configContextType in ConfigCreator instead of optionsType ### Salesforce Adapter - Salesforce Data Instances CV in the context of the deploying user - Adding support for custom references in additional profile sections: categoryGroupVisibilities, customMetadataTypeAccesses, customPermissions, externalDataSourceAccesses - Improved IA between LightningPages and CustomFields - Improved IA between Flow and CustomFields - generate dependencies of metadata instances by formula fields ### Okta Adapter - Add support for Okta Admin console session settings - Support managing tenant features via Salto - Support managing Threat Insights configurations - Fix a bug in deployment of Group Push, blocking deployment of group push if the group is mapped to a different app - Fix a bug in additions of GroupPush ### Jira_adapter - Prepared the removal of 'Enable JSM' checkbox for Jira DC based on a given Jira config context - Remove null values from dashboard gadgets - Added support to references in advanced fields in automations - Added support for missing references in ScriptRunner scripts - Users will not be able to deploy additions of provisioning field in application - Add a log to identify customers that have contexts with over 10K options - Fix field type in `jira.FieldConfiguration` - Users can now safely deploy forms that include default form fields - Fixed a bug with deployment of same-name cascading options - Fixed a bug with deployment of fieldContextOption - Solved a bug with deployment of automation when parseAdditionalAutomationExpressions is on - Fixed a bug with deployment of default values for field contexts - Automation collaborators will now be sorted - Deployment of JSM fields that can be created by Atlassian will be blocked ### Netsuite Adapter - Fix SuiteApp files counts query fails - when `fetch.fetchPluginImplementations` is `true`, plugin implementation instances will be fetched ### Microsoft Security Adapter - Fix a bug in deployment of Intune ScopeTags when deploying concurrently multiple tags - Fix EntraAppRole deploy on addition ## Expected changes to existing workspaces ### Okta Adapter - Okta Admin console session settings will be added - Threat Insights configuration will be added to workspace ### Salesforce Adapter - Fixed a bug that in some rare cases could have caused profile values to be dropped - References will be added from UiFormulaCriterion (LightningPage) to CustomField - References will be added from Flow to CustomFields ### Jira Adapter - null values will be removed from dashboard gadgets on the next fetch - customfields IDs in advacedFields (in automation type) will become references. - ScriptRunner scripts that uses missing custom fields will be replaced with missing references - Prevent failed deployments of contexts due to an existing context with overlapping project scope - The default answer field in the forms NACL has been updated. It previously stored 'choices' as a list of string IDs. It has now been updated to use a list of key-value objects, where the IDs have been converted to references - Automation collaborators will now be sorted ### NetSuite adapter - when `fetch.fetchPluginImplementations` is `true`, plugin implementation instances will be fetched
Bump to version 0.4.6 (#6820) # Salto Version 0.4.5 ## New features and bug fixes ### Core - Improved dangling static files removal process. - Updated logic for returning detailed changes when the primitive type changes entirely. - Adjusted parameters for `isInitializedFolder` and `initFolder` methods to exclude `workspace`. ### Salesforce adapter - Fixed incorrect references from WorkflowRule instances to RecordType instances (requires enabling `removeReferenceFromFilterItemToRecordType` feature). - Addressed an issue with Active Flow Versions' incorrect internal IDs, improving `Go To Service` and `extraDependencies` behavior. - Enhanced compatibility with more types for changes in SFDX project folders. - Introduced methods to verify and create SFDX projects in directories. ### Okta adapter - Added fetch and deploy support for brand-customized sign-in and error pages. - Supported priority changes for Authorization Server policies and rules. - Resolved a bug causing issues with priority updates in Authorization Server policy rules. ### Zendesk adapter - Added a feature to deploy all articles as drafts (`{ fixElements: { deployArticlesAsDraft: true } }`). - Trigger actions `set_skills` and `add_skills` now prioritize required/optional as per Zendesk API updates. ### Jira adapter - Restructured workflow transitions, replacing `to` and `from` fields with `links` and `toStatusReference` per Atlassian API updates (Jira Cloud). ### Jamf adapter - Implemented service URL support. ### Miscellaneous - Dummy adapter now supports `loadElementsFromFolder` function. ## Expected changes to existing workspaces ### Salesforce adapter - Enabling `removeReferenceFromFilterItemToRecordType` may remove existing references. - Updates in `_generated_dependencies` of Flow elements may occur. ### Okta adapter - NaCL files for customized brand pages will be introduced. - Priority instances for Authorization Server policies may reflect changes. ### Zendesk adapter - Articles will omit `draft` and `locale` fields, managed via translations. - Trigger NaCLs will now reflect priority keys for `set_skills` and `add_skills` actions. ### Jira adapter - Workflow transitions now reflect `links` and `toStatusReference` fields, aligning with Atlassian's updates.
PreviousNext