Salto v0.4.9

Salto Version 0.4.9

New features and bug fixes

Core

• Omit conflicts on _generated_dependencies
• fetch function has been updated to use named arguments instead of positional arguments.
• preview function has been updated to use named arguments instead of positional arguments.
• addAdapter function has been updated to use named arguments instead of positional arguments.
• deploy function has been updated to use named arguments instead of positional arguments.
• getDefaultAdapterConfig function has been updated to use named arguments instead of positional arguments.
• getAdaptersCredentialsTypes function has been updated to use named arguments instead of positional arguments.
• Bugfix: added or removed field annotations now have correct side effects for hiding or unhiding instance field values.

Local Workspace

• initLocalWorkspace function has been updated to use named arguments instead of positional arguments.
• localAdaptersConfigSource function has been updated to use named arguments instead of positional arguments.

Workspace

• Reduce memory consumption in mergeManager cache update
• loadWorkspace function has been updated to use named arguments instead of positional arguments.
• initWorkspace function has been updated to use named arguments instead of positional arguments.

Adapter Creators

• Create a new package called adapter-creators

Jira adapter

• Fixed a bug with some Board Deployments. Also, Board will now include also the Backlog built-in column
• Added new CV to limit duplication of global transitions
• Remove tags from Automations
• Mask 'Authorization' and 'x-api-key' Automation headers by default

Microsoft Security adapter

• Fix pending changes on the app role id post addition
• Omit credential fields (keyCredentials, passwordCredentials, tokenEncryptionKeyId) from Entra Application & Service Principal.
• Block the creation of on-prem groups.
• Add missing references to Authentication Strength Policies.

NetSuite adapter

• Remove warnings from SDF error message
• Return SDF warnings on deploy/validation
• Mark custom records as singletons using the fetch.singletonCustomRecords adapter config.
• Make locked custom record types visible (with adapter config visibleLockedCustomRecordTypes).
• Resolve ASVs for referenced builtin field types

Okta adapter

• Add support in UserRoles type, which includes all admin roles assigned to a user.
• Support deployment of Authorization server with all of its claims
• Users will see oAuth2ScopeConsentGrants filed in Application that have signOnMode = "OPENID_CONNECT" and have active grants.

Salesforce adapter

• Added support for listing deprecated CVs in deploy config.
• Reduced the severity of listing a CV that doesn't exist in the delpoy config from an error to a warning.
• Implemented support for canceling task of type validation or deployment.
• Add parent relationship to Record-Triggered Flows.
• Added references from FlowAssignmentItem (Flows) to CustomField under the feature addParentToRecordTriggeredFlows in optionalFeatures
• Improve SBQQ__ProductOption__c alias.

Expected changes to existing workspaces

Salesforce adapter

• _parent annotation will be added to Record-Triggered Flows.

• Added references from FlowAssignmentItem (Flows) to CustomField under the feature addParentToRecordTriggeredFlows in optionalFeatures
• Tha alias for SBQQ__ProductOption__c instances will change.

Jira adapter

• Board NaCls will now include also the built-in backlog column
• Remove tags from Automations
• Mask 'Authorization' and 'x-api-key' Automation headers by default

Microsoft Security adapter

• The following fields will no longer be fetched for Entra Application & Service Principal instances: keyCredentials, passwordCredentials, tokenEncryptionKeyId.
• The authenticationStrength field under conditional access policies will now be replaced with a reference to the matching authentication strength policy.

NetSuite adapter

• Instances of custum record types that will be added to fetch.singletonCustomRecords will change their element ID to match the type.
• With the adapter config visibleLockedCustomRecordTypes, locked custom record types will be visible in the workspace, with the isLocked = true annotation.
• Resolve ASVs for referenced builtin field types using the following config:

netsuite {
  ...
  suiteAppClient = {
     additionalSuiteQLTables = [
        ...
        {
           name = "fieldType"
           typeId = "-213"
        },
     ]
  }
}

Okta adapter

• On the next fetch, a config change will exclude UserRoles type. To include to, explicitly add an entry in the adapter nacl file:

okta {
   fetch = {
       include = [
          { type = ".*" },
          { type = "UserRoles" }
       ]
   }
}

• System claims that are not visible in the Okta Admin Console, will be deleted from the Salto workspace
• Users will see oAuth2ScopeConsentGrants filed in Application that have signOnMode = "OPENID_CONNECT" and have active grants.