Open jasric89 opened 2 years ago
Please can I get an update on this issue? Thank you
@jasric89 Thanks for raising the issue. Are you suggesting the subject_filter
property or any other filter such as filters defined in included_event_types
was not updated as expected?
@xiaxyi yes that is what I am trying to explain. The field: included_event_types = [""]
Does not update if you add a new filter to the included event type.
If you make the azurerm_eventgrid_event_subscription
from scratch, with the event types in it, terraform will make the resource.
If you want to update one, terraform will not update it.
As a work around for now I have to go into the portal and delete the eventgrid subscription and then run the terraform command, either from a pipeline or teraform apply -auto-approve
then terraform will make the whole subscription with the new filters in.
We see a similar issue at our end.
included_event_types = [ "Any Event" ]
included_event_types = [ "Any Event" ]
completely from the resourceExpected: Terraform should detect the removal and delete the filters from the resource. Observed: Terraform does not delete the filter ever.
Please can I get an update on when this will be fixed please?
Is there an existing issue for this?
Community Note
Terraform Version
1.1.7
AzureRM Provider Version
3.14.0
Affected Resource(s)/Data Source(s)
resource "azurerm_eventgrid_event_subscription" "sub_nsclassroom_toTechnicianApi" {
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
For the Provider to write in the new filters. There is no panic output.
Actual Behaviour
It seems that if you have an existing event grid subscription made with Terraform and then decide to add in a new filter. The provider sees there is a change but does not pick up the filter as a change. Therefore when getting to an apply it does not add in the new filter.
If you create the event grid subscription from scratch with all the new filters it creates it fine. It's only when updating the event grid subscription the problem occurs. This first occurred to me on provider 2.95.0 so I upgraded to 3.1.4 and the same thing happens.
Please can this be investigated?
Steps to Reproduce
See note above
Important Factoids
no
References
No response