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

Doesn't work in private networks #85

Open
cpen-blm opened this issue Apr 25, 2023 · 3 comments
Open

Doesn't work in private networks #85

cpen-blm opened this issue Apr 25, 2023 · 3 comments

Comments

@cpen-blm
Copy link

There is a need to have pre-configured storage when the requirement is to use private networking. Please update to include the option to have storage pre-deployed prior to this app and to be able to select that storage.
This errors our with:
{
"status": "Failed",
"error": {
"code": "BadRequest",
"message": "Creation of storage file share failed with: 'The remote server returned an error: (403) Forbidden.'. Please check if the storage account is accessible.",
"details": [
{
"message": "Creation of storage file share failed with: 'The remote server returned an error: (403) Forbidden.'. Please check if the storage account is accessible."
},
{
"code": "BadRequest"
},
{}
]
}
}

@RobSwoss
Copy link

We have the same problem. We also tried to create the storage account beforehand. Unfortunately this didn't work.

@oramoss
Copy link

oramoss commented Jul 27, 2023

Yes, can't use this when we want our resources vnet injected.

@cpen-blm
Copy link
Author

Then this is unusable in orgs that require privtae networking and perhaps zero trust which is unfortunate.
If you cannot fix that could you please place that info in the readme as pre-reqs?
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants