Mass ingest
One of the first steps of integrating your code with Moderne is setting up a pipeline that builds and publishes LST artifacts to an artifact repository that you control.
Configuring Moderne DX
Moderne DX is a secure, fully on-premises, enterprise-level automated code remediation solution. At its heart is a central service that must be configured for everything to work correctly. This guide will walk you through how to do that.
How to create a DevCenter locally
The Moderne DevCenter gives you high-level details about the state of all of your repositories. If you don't have access to the Moderne Platform, but you want to create a DevCenter locally, you can do so with the Moderne CLI.
Configure Moderne DX with Maven repository access
In order for Moderne DX to get the list of your Lossless Semantic Tree (LST) and recipe artifacts, the service needs to be configured to talk to your Maven-formatted artifact repositories. There are a variety of services that support repositories in this format. Some examples include JFrog Artifactory, Sonatype Nexus, and Azure Artifacts.
Configure Moderne DX with Artifactory access: LSTs
Artifactory serves as a source of LST artifacts. This integration uses Artifactory Query Language (AQL) to identify LST artifacts.
Configure Moderne DX with Artifactory access: recipes
In order for Moderne DX to interact with your recipe artifacts from Artifactory, you will need to create a Maven formatted repository inside of Artifactory and point the Moderne DX service to said repository. This guide will walk you through how to configure the Moderne DX service to get the list of recipe artifacts from the repository you created in Artifactory.
Configure on-prem source code management (SCM) with Moderne DX
In order for Moderne DX to correctly map repository clone URLs to the right origin and path you will need to provide the base URL(s) for your SCM server. For SaaS SCM services like GitHub, GitLab, Bitbucket (cloud) and AzureDevOps – no extra configuration is required. For on-prem SCM servers, though, you will need to provide Moderne with additional information. Specifically the type, base URL, and any alternate URLs that are used to access the server.
Configure Organizations with Moderne DX
Many users desire the ability to dynamically control the organizational structure (repository groupings) of their repositories within Moderne DX. There are two ways to achieve this, either by supplying DX with a file describing the organizational structure (via a repos.csv) or by integrating with an organization service.
Configure Moderne DX with strict recipe sources
The Moderne CLI is configured to use the following Maven repositories to load recipe artifacts from in the event the Moderne DX service has not been configured with any recipe sources or if a recipe artifact cannot be sourced from what is configured.
Deploying recipe artifacts in Moderne DX
Deploy using the Moderne GraphQL API
Configure Moderne DX service with client SSL certificates
If you are configuring the Moderne DX service to connect to a service that requires a self-signed certificate to perform an HTTPS request (e.g., Maven or Artifactory) you will need to:
All DX configuration variables
This document includes all of the variables you can configure the Moderne agent to run with. Your configuration will only use some of these.