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

logic app http trigger with a parameterised relative path raises error #1917

Closed
alastairtree opened this issue Sep 12, 2018 · 1 comment
Closed

Comments

@alastairtree
Copy link
Contributor

alastairtree commented Sep 12, 2018

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.11.7
provider.azurerm v1.14.0

Affected Resource(s)

  • azurerm_logic_app_trigger_http_request

Terraform Configuration Files

resource "azurerm_logic_app_trigger_http_request" "http_trigger" {
  name         = "some-http-trigger"
  logic_app_id = "${module.logic_app_workflow.id}"
  method="GET"
  relative_path="customers/{customerID}"
  schema = <<SCHEMA
{}
SCHEMA
}

Expected Behavior

Creation the trigger with a logic app parameter in the relative path

Actual Behavior

Error output:
Error: azurerm_logic_app_trigger_http_request.http_trigger: Relative Path can only contain alphanumeric characters and underscores.

Steps to Reproduce

See https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-http-endpoint#accept-parameters-through-your-http-endpoint-url for a logic app example

@ghost
Copy link

ghost commented Mar 6, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants