Skip to content

Salto v0.3.55
Compare
Choose a tag to compare
@saltoio saltoio released this 11 Apr 07:52
· 1213 commits to main since this release
v0.3.55
c7ee361
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Salto Version v0.3.55

New features and bug fixes

Core

  • Stop creating additionalProperties field upon fetch
  • Save reference to a type in additional_properties annotation
  • Keep additional properties annotation from swagger and stop creating a field additionalProperties
  • addAlias function is no longer supports secondInterationsTypes parameter, instead it builds a dependencies graph

Salesforce adapter:

  • Retrying SFDC requests on "security policies took too long to evaluate".
  • Retrying SFDC requests on disconnect/reset before headers.
  • Do not suggest to exclude types with many instances that are under allowReferenceTo.
  • Automatically retrying requests which fail with a 406 status. We are seeing these errors in the wild and they are always resolved by retrying.
  • Fetch with delta now works for data records of types listed in allowReferenceTo
  • Support for Go To Service for Auto Response Rules elements.
  • Better handling of internal Salesforce errors.
  • The Translations type is now excluded from fetches in new workspaces.
  • Add Change Validator that forbids changes on fields of Task and Event.
  • DiscoveryAIModel metadata type is excluded in new workspaces
  • Implemented a Change Validator that notifies users that the adapter will enable the FLS to certain Profiles on addition of new CustomField or CustomObject

NetSuite adapter:

  • Fixed change validator messages that wrongly contained element names
  • Fix elements will now remove permissions with unresolved references
  • Do not classify testing accounts as production

Zendesk adapter:

  • Add reference to skills in trigger actions
  • Stop showing Article Label ordering in deployment changesets
  • Add a new validator that emits errors when custom statuses are disabled for the account but used in view conditions.
  • Enable deployment of __NULL__ as user
  • Add validation that an automation order isn't empty.
  • Enable modification of default_locale in articles, categories and sections in the Zendesk guide
  • Fix bug where non-"Dynamic content item" strings were being parsed as dynamic content and creating broken references
  • Added a config flag which allows omitting the Ticket_status_custom_status ticket field from Ticket Forms on fetch
  • Fixed a bug where there were duplicate usernames from instance fields

Okta adapter:

  • When deploying Device Assurance Policies with dynamic OS constraints, verify the dynamic OS feature is enabled in the target account
  • Allow filtering instances using fetch criteria by type, status, and group names. For example, to exclude all inactive apps, use: 
    okta = {
  fetch = {
    ...
    exclude = [
      {
        type = "Application"
        criteria = {
          status = "INACTIVE"
        }
      }
    ]
  }
}
  • Add the option to deploy group membership changes for existing users. To enable this feature, add fetch.includeGroupMemberships to your adapter configuration file
  • Fix an issue with deployment of default authentication policies in certain cases. To resolve, run next fetch with regenerate elemIDs
  • Added support for addition and removal of Brand elements
  • Fix bug in deployment of Access Policy Rules with required field set
  • In new environments, ProfileMapping properties object will not be fetch by default, and can be included by turning includeProfileMappingProperties flag to true. Existing envs will not be affected.
  • ProfileMapping now supports removal action in deployment.

Confluence adapter:

  • First version is ready to use

Google Workspace adapter:

  • First version is ready to use

Jira adapter:

  • Add assets component in Automation.
  • Now support fetching and deploying issue type icons.
  • Fixed duplication error that arose from a bad response for Calendar instances.
  • Now support fetch and deploy of objectType icons.
  • Fixed error throwing in gqlPost for requestForm.
  • ObjectSchemaDefaultReferenceType can be deployed.
  • Team-managed boards will not be fetched
  • Team-managed projects will not be deployable
  • Fixed a bug that caused a validation error when changing the deploy config fields: taskMaxRetries and taskRetryDelay
  • Fixed a bug that could cause partial success for deployments

Expected changes to existing workspaces

Jira adapter:

  • For automation nacls: serviceDesk field will be removed and requestType field will be converted from string to reference expression.
  • Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Notification Events, Workflows and maybe more)
  • Users will see new fields in their issueType nacls named avatar.
  • New nacls of type ObjectTypeIcon will appear in the users next fetch.
  • Forms nacls portalRequestTypeIds field will be changed from numbers to reference expression.
  • Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Notification Events, Workflows and maybe more)
  • objectSchema nacls will have new field called properties
  • Team-managed boards will be removed from users' environments

Okta Adapter:

  • Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Users, GroupRule, PasswordPolicyRule and maybe more)
  • The members list in GroupMembership instances will be sorted
  • When running fetch with regenerate elemIDs, elemID for the default access policy will change
  • Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Users, GroupRule, PasswordPolicyRule and maybe more)

Zuora billing Adapter:

  • Instances with additionalProperties map field will be flatten upon fetch

Stripe Adapter:

  • Instances with additionalProperties map field will be flatten upon fetch
Assets 6
Loading