-
Notifications
You must be signed in to change notification settings - Fork 12
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
[AVM Module Issue]: #61
Comments
Hi @vjmanda - I am currently working on a pattern module for function apps using secured storage. I believe the current workaround would be to leverage the function app resource module along with the storage account resource module. |
@donovm4 - Should it be a pattern module though just to connect from the function app to backend storage securely? |
@vjmanda - one of the main factors for a pattern module being created is to aligned with this quickstart template for creating a Function App with private endpoint-secured Storage. From my understanding, it would also be outside of the scope / spec to load up the resource module for In this case, the separate resource modules for a storage account and function app have already been developed, so it would be easier to reference both modules individually to work together or use a pattern for a common task involving these resources, rather than duplicate the capabilities of the storage account module into the function app module. Here is the original proposal Feel free to open up an issue on AVM GitHub if you would like to provide feedback / insight on this particular issue. |
Thanks @donovm4 - I will take a look at the pattern module proposal. |
Warning Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly. Tip
Note This message was posted as per ITA01TF. |
Warning Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly. Tip
Note This message was posted as per ITA01TF. |
Caution **This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days. ** Tip
Note This message was posted as per ITA02TF. |
Warning Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly. Tip
Note This message was posted as per ITA01TF. |
Caution **This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days. ** Tip
Note This message was posted as per ITA02TF. |
This module is still in development, and will be running through a code review in the near future |
Check for previous/existing GitHub issues
Issue Type?
Feature Request
Feature request
Allow configuring private endpoints for the function app's backend storage account.
Description
The module currently only permits creating the function app's backend storage account publicly with no restrictions. This is the case even when the function app is configured with private endpoints.
Ideally the module should permit the function app to connect to the backend storage account privately using private endpoint connectivity.
The text was updated successfully, but these errors were encountered: