Aspire 5 has changed the way crawls can be configured, in previous version the notion of a "content-source" involved configuring the connection to the repository, credentials, seed URLs, workflow processing, scheduling, etc. In Aspire 5, the content source was replaced with a set of interconnected configuration objects. See Aspire 5.0 Architecture for more details
Follow the instructions at Migration guide
The Group Expansion service was replaced in Aspire 5 with a Group Expansion connector, which takes the identities cached in the NoSQL database by the connectors/identity crawlers (such as Azure AD, LDAP, Confluence, etc), and expands the group memberships recursively. It is important to notice that those expanded entities are not stored in the identity cache and that the user can add a publisher on the Workflow to store them, so it can be picked by the external search application to perform security trimming on search results. For more information on how this works, please check the Group Expansion Connector documentation.
Aspire 5 provides an official docker image so it can easily be used in deployments on container orchestration frameworks such as Kubernetes. See Kubernetes Deployments and Quickstart Guide with Docker (HTTPS)
You can contact Aspire Support Team at [email protected], or at the designated contact media on your Aspire Support contract.
Aspire Support may assist you on identify what the issue really is, but if the issue is detected at a customized groovy script at your workflow configuration, that isn't considered in Support Scope.