Configuring the Moderne agent
In order to securely communicate with the Moderne SaaS, you will need to set up an on-premise agent in your environment. To assist you with that process and provide you with information about the agent, this guide will:
Configure an agent with Azure DevOps Services
In order to view recipe results and commit changes from a recipe back to Azure DevOps Services, you'll need to register a Microsoft Entra ID OAuth app and configure the Moderne agent with the appropriate variables.
Configure an agent with Bitbucket Data Center access
In order to view recipe results and commit changes from a recipe back to Bitbucket, you'll need to create an application link in Bitbucket and configure the Moderne agent with the appropriate variables.
Configure an agent with Bitbucket Cloud access
In order to view recipe results and commit changes from a recipe back to Bitbucket, you'll need to create an application link in Bitbucket and configure the Moderne agent with the appropriate variables.
Configure an agent with GitHub
In order to view recipe results and commit changes from a recipe back to GitHub, you'll need to create a GitHub OAuth app and configure the Moderne agent with the appropriate variables.
Configure an agent with GitLab
In order to view recipe results and commit changes from a recipe back to GitLab, you'll need to create a GitLab OAuth app and configure the Moderne agent with the appropriate variables.
Configure an agent with Maven repository access
In order for Moderne to retrieve your Lossless Semantic Tree (LST) or recipe artifacts, the agent needs to be configured to talk to your Maven-formatted artifact repositories. This connection also allows Moderne to lookup dependency versions to determine if a new version is available.
Configure an agent with Artifactory access: LSTs
Artifactory serves as a source of LST artifacts for Moderne. This integration uses Artifactory Query Language (AQL) to identify LST artifacts that have not yet been encrypted and transmitted to Moderne in near real-time.
Configure an agent with Artifactory access: recipes
In order for Moderne to retrieve your recipe artifacts from Artifactory, you will need to create a Maven formatted repository inside of Artifactory and point the agent to said repository. This guide will walk you through how to configure the agent to get recipe artifacts from your repository.
Configure an agent with PyPI access: visualizations
In order for Moderne to retrieve your visualization artifacts from PyPI, you will need to configure the agent and run it in a specific environment. This guide will walk you through how to configure the agent to get visualization artifacts from your PyPI package index.
Configure the agent with the Organizations service
In order for Moderne to obtain information about your organizational structure, you will need to configure the Moderne agent to point to your Organizations service. This guide will explain how to do that.
Configure an agent with generic HTTP tools for use in recipes
You have internal services within your enterprise that you may want to use within your recipes. Some possible examples follow:
Configure an agent with strict recipe sources
The Moderne SaaS is configured to use the following Maven repositories to load recipe artifacts from in the event the agent has not been configured with any recipe sources or if a recipe artifact cannot be sourced from what is configured. (Requires agent version 0.118.0 or greater)
Configure an agent with client SSL certificates
If you are configuring the Moderne agent to connect to a service that requires a self-signed certificate to perform a HTTPS request (e.g., Maven or Artifactory) you will need to:
Configure an agent to connect to Moderne via an HTTP proxy
If your organization requires an HTTP proxy in order to be able to access the public internet, you can configure this proxy for communication between the Moderne Agent and the Moderne API Gateway.
All agent 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.
Multi-tenant private recipes
The instructions on this page will only apply to you if: