Add Sonatype Nexus Repository Integration Module

Summary

Implements a Coder module for Sonatype Nexus Repository Manager integration that automatically configures Maven, npm, PyPI, and Docker registries for development workspaces.

Demo Video & Screenshots

Features

• ✅Maven Support: Automaticsettings.xml configuration
• ✅npm Support: Automatic.npmrc configuration with scoped packages
• ✅PyPI Support: Automaticpip.conf configuration
• ✅Docker Support: Registry authentication setup
• ✅Flexible Configuration: Support for multiple repositories per package manager
• ✅Secure Credentials: API token and password support
• ✅Username Options: Configurable username field (username or email)

Nexus Repository Manager Requirements

Version Requirements

Yes, this module requires Nexus Repository Manager Pro version for full functionality, though basic features work with the Community Edition (OSS).

Supported Authentication Methods

This module supports4 authentication methods:

1. User Token Authentication (Recommended - Pro only)

   • Enhanced security with two-part tokens
   • Ideal for CI/CD and automated environments
   • Requiresnx-usertoken-current privilege

2. API Token Authentication (Pro only)

   • Single-use access tokens via REST API
   • Programmatic token generation and management

3. Basic Authentication (OSS & Pro)

   • Standard HTTP Basic Auth with username/password
   • Works with both OSS and Pro versions

4. Base64 Encoded Credentials (OSS & Pro)

   • Base64 encodedusername:password format
   • Compatible with npm and other package managers

Testing Instructions

Prerequisites

• Nexus Repository Manager instance (OSS or Pro)
• Admin access to configure repositories
• Test repositories for each package manager you want to test

Setup Test Environment

1. Create Test Repositories in your Nexus instance:

   • Maven:maven-public,maven-releases
   • npm:npm-public,@company:npm-private
   • PyPI:pypi-public,pypi-private
   • Docker:docker-public,docker-private

2. Configure Authentication:

   • For Pro: Generate user tokens via UI (User menu → User Token)
   • For OSS: Use username/password or base64 encoded credentials
   • Set up appropriate permissions for test repositories

3. Test the Module:

   module"nexus" {source="registry.coder.com/mavrickrishi/nexus/coder"version="1.0.0"agent_id=coder_agent.main.idnexus_url="https://your-nexus-instance.com"nexus_password=var.nexus_api_token# or passwordpackage_managers={    maven= ["maven-public","maven-releases"]    npm= ["npm-public","@company:npm-private"]    pypi= ["pypi-public","pypi-private"]    docker= ["docker-public","docker-private"]  }}

4. Verify Configuration:

   • Check generated config files in workspace
   • Test package installation from configured repositories
   • Verify authentication works for each package manager

EC2 Deployment Testing

Tested by deploying on EC2 instance with:

• Ubuntu 22.04 LTS
• Nexus Repository Manager Pro
• All package managers (Maven, npm, PyPI, Docker)
• Both token and basic authentication methods

Usage Example

module"nexus" {source="registry.coder.com/mavrickrishi/nexus/coder"version="1.0.0"agent_id=coder_agent.main.idnexus_url="https://nexus.company.com"nexus_password=var.nexus_api_tokenpackage_managers={    maven= ["maven-public","maven-releases"]    npm= ["npm-public","@company:npm-private"]    pypi= ["pypi-public","pypi-private"]    docker= ["docker-public","docker-private"]  }}

Testing

• ✅ 11 comprehensive tests covering all functionality
• ✅ Variable validation tests
• ✅ Package manager configuration tests
• ✅ Error handling tests
• ✅ All tests passing
• ✅ EC2 deployment tested

Files Added

• registry/mavrickrishi/modules/nexus/main.tf - Main module configuration
• registry/mavrickrishi/modules/nexus/README.md - Complete documentation
• registry/mavrickrishi/modules/nexus/main.test.ts - Test suite

Checklist

• Module follows existing patterns and conventions
• Comprehensive test coverage (11 tests)
• Complete documentation with examples
• Input validation and error handling
• Secure credential handling
• All tests passing
• Demo video included
• Screenshots added
• Testing instructions provided
• Authentication methods documented
• EC2 deployment tested

Closes#202
/claim#202