You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2020. It is now read-only.
I need to be able to deploy to a local resource, and instead of opening up an inbound connection to our network I'm looking at using a concourse worker to facilitate the deployment.
In order to get this to work, I had to add inbound port 2222 to the concourse-up-ant-ci-atc aws security group.
However, the self-update just blasted this change away. ;-)
What's the reason this port hasn't been exposed and is there a way I can have this change persisted across releases?
Cheers,
Adam
The text was updated successfully, but these errors were encountered:
Hi,
I need to be able to deploy to a local resource, and instead of opening up an inbound connection to our network I'm looking at using a concourse worker to facilitate the deployment.
In order to get this to work, I had to add inbound port 2222 to the
concourse-up-ant-ci-atc
aws security group.However, the self-update just blasted this change away. ;-)
What's the reason this port hasn't been exposed and is there a way I can have this change persisted across releases?
Cheers,
Adam
The text was updated successfully, but these errors were encountered: