Skip to content

Add JFrog Artifactory support as alternative to Azure Container Registry #187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
omarmciver wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Add JFrog Artifactory support as alternative to Azure Container Registry #187

omarmciver wants to merge 4 commits into from

Conversation

@omarmciver
Copy link

@omarmciver omarmciver commented Jan 23, 2026

Summary

  • Add deployment scripts and infrastructure templates for using JFrog Artifactory as the container registry
  • Enable pulling .NET 9.0 base images from JFrog (mirrored/proxied from MCR)
  • Support local Docker builds with push to JFrog, replacing ACR Tasks cloud builds

Motivation

  • Some organizations use JFrog Artifactory as their centralized artifact repository rather than Azure Container Registry. This change provides an alternative deployment path that:
    • Integrates with existing JFrog infrastructure
    • Allows local Docker builds
    • Uses username/password authentication compatible with JFrog API keys

omarmciver and others added 3 commits February 9, 2026 12:01
@omarmciver
Add JFrog support for enterprise lockdown environments
1c3f02b
@omarmciver
Feature: Update JFrog deployment scripts and Dockerfile for improved …
9e68b92 
…security and functionality

- Enable private endpoint access in Bicep configuration
- Disable insecure ingress in container app settings
- Enhance deployment script with additional parameters for JFrog repository management
- Update Dockerfile to support NuGet authentication and MongoDB tools installation
- Include MongoDB Database Tools tarball for local build context
@omarmciver
Feature: Add optional StateStore connection string parameter and defa…
21d5dfc 
…ult value for Debian distribution
@omarmciver omarmciver force-pushed the feature/jfrog-registry branch from c9e772f to 21d5dfc Compare February 9, 2026 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@omarmciver