<p>So I found similar question (regarding installing, but works for publishing as well) <a href="https://stackoverflow.com/questions/73624685/install-python-package-from-private-artifactory-behind-vpn">https://stackoverflow.com/questions/73624685/install-python-package-from-private-artifactory-behind-vpn</a></p>
<p>Basically, you can either setup GH Actions runner within VPN or use proxy to access your resorces.</p>
<p>I have ended up using answer from comments</p>
<blockquote>
<p>my strategy would be to create a source code release zip file and publish it on GitHub and then download it from within the VPN to push it to the intern repository. github.com/marketplace/actions/create-github-release</p>
</blockquote>
<p>and still run separate job for publishing into internal repository.</p>

CC BY-SA 4.0
2022-09-19T12:12:27.210Z
2022-09-19T12:12:27.210Z
GopherM
<p>I'm using Github Actions to publish my python packages automatically. When working with PyPI everything works fine and providing different config to point on different repository is not an issue.
But when repository (JFrong artifactory) is located behind VPN GH Actions is not able to push/fetch from there.</p>
<p>What is the right approach to deal with such kind of situation? Is there any kind of existing solution for this issue?</p>

CC BY-SA 4.0
2022-09-03T12:41:10.790Z
The difficulty with this action is that VPN requires certificates to establish the connection and creates a new network dynamically which then gives you access to the subnetwork by routing your request. Now GH actions run in a container bases serverless environment behind a peripherical firewall so most likely you will not be able to change the network configurations because it needs ` root ` access.
Bodo Hugo Barwich
CC BY-SA 4.0
2022-09-03T15:26:11.233Z
@BodoHugoBarwich is it possible to spawn some kind of a tunnel withing the agent/container?
GopherM
CC BY-SA 4.0
2022-09-03T17:48:10.897Z
my strategy would be to create a source code release zip file and publish it on GitHub and then download it from within the VPN to push it to the intern repository. https://github.com/marketplace/actions/create-github-release
Bodo Hugo Barwich
<python><aws-vpc><artifactory><github-actions><vpn>
Publish python package into private repository behind VPN
GopherM
# Publish python package into private repository behind VPN

(Asked by: username_0 on 2022-08-30)

I'm using Github Actions to publish my python packages automatically. When working with PyPI everything works fine and providing different config to point on different repository is not an issue.
But when repository (JFrong artifactory) is located behind VPN GH Actions is not able to push/fetch from there.

What is the right approach to deal with such kind of situation? Is there any kind of existing solution for this issue?

**Tags:** python, aws-vpc, artifactory, github-actions, vpn

> **Comments:**
> **username_1**: The difficulty with this action is that VPN requires certificates to establish the connection and creates a new network dynamically which then gives you access to the subnetwork by routing your request. Now GH actions run in a container bases serverless environment behind a peripherical firewall so most likely you will not be able to change the network configurations because it needs ` root ` access.  
> **username_0**: @BodoHugoBarwich is it possible to spawn some kind of a tunnel withing the agent/container?  
> **username_1**: my strategy would be to create a source code release zip file and publish it on GitHub and then download it from within the VPN to push it to the intern repository. https://github.com/marketplace/actions/create-github-release  

---

## 1 answers

### Answer by username_0 on 2022-09-19. Score: 0

So I found similar question (regarding installing, but works for publishing as well) <https://stackoverflow.com/questions/73624685/install-python-package-from-private-artifactory-behind-vpn>

Basically, you can either setup GH Actions runner within VPN or use proxy to access your resorces.

I have ended up using answer from comments

> my strategy would be to create a source code release zip file and publish it on GitHub and then download it from within the VPN to push it to the intern repository. github.com/marketplace/actions/create-github-release

and still run separate job for publishing into internal repository.


---

