-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
New resource: azurerm_logic_app_standard
#13196
New resource: azurerm_logic_app_standard
#13196
Conversation
@jackofallops @dylanmorley I cannot tell from what I can see here but does this support App Service Enviroment v3? |
@adamyager not something I explicitly tested, but this issue (#12537) seems resolved for function_app which azurerm_logic_app_standard is heavily based upon, so I'd expect this would work in a similar config. |
ok. I get it. As long as I use app_service_plan_id for the Logic app, it "should" work? Thanks for the quick response. |
hey @dylanmorley This PR looks great, only a suggestion. So should be useful to allow to set kind property |
@jcanizalez yeah I did think about doing that. However, I went for the resource 'managing' the kind as a design choice - I thought in general it would be preferable to slightly abstract users of the resource from some of the complexities of configuration combinations in order to create the right logic app types There are couple of examples of this in the resource - I did the same for a number of config settings. Instead of expecting you to have to set app_settings for APP_KIND, workflow bundles etc, the resource creates and manages these for you, which keeps all of these repetitive settings out of everyone's implementations. I thought this would result in slightly cleaner HCL - you'd just need to supply the minimum amount of parameters to get the right type created. Any thoughts on this approach - or would you just prefer to be able to (and have to) specify everything yourself? For this scenario, following the same pattern in this PR we could expose 'Extended Location' as a property, and if it's supplied with linuxFxVersion then kind would be "kubernetes,functionapp,workflowapp,linux". |
Thanks for your response @dylanmorley Make sense, we can implement support for Logic Apps on Azure ARC later once this PR was release |
@katbyte |
Is this already available to be used on the latest release? Thank you guys. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @dylanmorley - at first glance i just had a couple comment son schema that i've left inline
Changes as per @katbyte suggestions done, latest test results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
azurerm_logic_app_standard
azurerm_logic_app_standard
This functionality has been released in v2.79.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Thanks @mbfrahry. I'm working extensively in this area at the moment, so any bugs or issues reported in this resource, tag me & I'll have a look. |
When will azurerm_app_service_virtual_network_swift_connection be updated to support azurerm_logic_app_standard @dylanmorley please? |
Oh no. It’s not supported in this release?
If that is the case, there is any alternative other than manual assignment?
On Fri, 1 Oct 2021 at 9:37 PM raptor75 ***@***.***> wrote:
When will azurerm_app_service_virtual_network_swift_connection be updated
to support azurerm_logic_app_standard @dylanmorley
<https://github.com/dylanmorley> please?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13196 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZ5Q5UWUJUS3WHYGN4VXOLUEXWXFANCNFSM5DEXZOHQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Melhores Cumprimentos,
Luis Simões
|
Never mind, just noticed that the documentation for azurerm_logic_app_standard mentions it to be used, but the documentation for azurerm_app_service_virtual_network_swift_connection is not yet updated to include azurerm_logic_app_standard. I am testing it myself right now anyway, hoping it works. And will update here. |
Let us know! Fingers crossed.
On Fri, 1 Oct 2021 at 9:44 PM raptor75 ***@***.***> wrote:
@dylanmorley <https://github.com/dylanmorley> @djpirra
<https://github.com/djpirra>
Never mind, just noticed that the documentation for
azurerm_logic_app_standard mentions it, but the documentation for
azurerm_app_service_virtual_network_swift_connection is not yet updated.
I am testing it myself right now anyway, hoping it works.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13196 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZ5Q5RD3N3IXHJOJZGQO4LUEXXOPANCNFSM5DEXZOHQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Melhores Cumprimentos,
Luis Simões
|
@djpirra it worked! |
Thanks for the good news!
Awesome work guys.
On Fri, 1 Oct 2021 at 10:25 PM raptor75 ***@***.***> wrote:
@djpirra <https://github.com/djpirra> it worked!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13196 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZ5Q5R5NDSWN5FWUJP5AVTUEX4JHANCNFSM5DEXZOHQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Melhores Cumprimentos,
Luis Simões
|
@dylanmorley I am facing an issue where the storage account blob structure is not consistently being created correctly when using this resource to create the logic app standard. This does not happen with function app. Is this a known issue please? |
@raptor75 Not anything I'm aware of, but please do open an issue and mention me in it, I'll have a look. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
As per #12023, creating a new resource azurerm_logic_app_standard to support Logic App Standard / Single Tenant model. While this is essentially a type of function_app (Logic app standard is built as an extension on top of the functions infrastructure), there is no attempt at reusing existing code as per the
function_app_resource
, instead favouring duplication of that code into the newazurerm_logic_app_standard
. This is because of rework happening in the web package for 3.0, so duplication was favourable to coupling & there is some behaviour specific to logic apps hosting that has been implemented here.azurerm_logic_app_standard
supporting both 'classic' and 'container' deploy models