Skip to content
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.

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

Airlock processor storage account - network restrictions? #4386

Open
jonnyry opened this issue Feb 20, 2025 · 3 comments · May be fixed by #4400
Open

Airlock processor storage account - network restrictions? #4386

jonnyry opened this issue Feb 20, 2025 · 3 comments · May be fixed by #4400
Labels
question Further information is requested

Comments

@jonnyry
Copy link
Collaborator

jonnyry commented Feb 20, 2025

Currently the airlock processor storage account has no network restrictions applied, despite having private endpoints.

Is there a reason for this? I'm not sure of the whole mechanism of the airlock and whether there's a problem with it using the private endpoints.

resource "azurerm_storage_account" "sa_airlock_processor_func_app" {

Image

Image

@jonnyry jonnyry added the question Further information is requested label Feb 20, 2025
@marrobi
Copy link
Member

marrobi commented Feb 20, 2025

Not that I'm aware of. does it seem to work fine with it disabled?

@jonnyry
Copy link
Collaborator Author

jonnyry commented Feb 20, 2025

Haven't tried - do the e2e tests cover the airlock?

@marrobi
Copy link
Member

marrobi commented Feb 20, 2025

Yes, extended does an import.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment