apache / apache/pulsar

[Enhancement] Support building Pulsar in restricted corporate environments without internet access

Open
#23,476 1 comment 0 reactions 0 assignees View on GitHub
type/enhancement
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Motivation

In restricted corporate environments, such as so called "air gapped" environments without internet access, builds must be able to use a given corporate maven repository which contains whitelisted dependencies and a corporate docker repository which contains whitelisted images.
It should be possible to build Apache Pulsar and docker images in such environments where the importance of software supply chain and source of origin is validated.

### Solution

- Make changes to the Pulsar build so that it doesn't require internet access for building Pulsar
- Make changes to the Pulsar build so that it doesn't require internet access for building a Pulsar docker image

### Alternatives

_No response_

### Anything else?

Apache Pulsar build should also be made reproducible, #23477

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

No files, tests, or build entry points are named. Start by auditing the Pulsar build and Docker-image build for network-dependent sources, then determine how corporate Maven and Docker repositories would be supplied. Done means both builds work without internet access using whitelisted dependencies and images.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
build-system, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
22/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.