Stoo Johnston

> did you change any of your code between using v2.49 of the provider and later versions? @thomas11 I must have done 🤔 Let me see if I can recreate...

I'm also experiencing this issue when I type: ``` `{: ``` As if I was documenting _how_ to write a link to a file. The issue happens every time with...

@t0yv0 tagging as requested. Thanks

`put_rest_api_mode="merge"` works around the disappearing policy because it won't recreate the `RestApi`, but it breaks updates to the api spec (which I'd argue is usually more important). The `merge` behaviour...

Sure thing. First file is me creating the JobSchedule with two parameters: - `"jobscheduletag01": "jobschedulevalue01"` - `"jobscheduletag02": "jobschedulevalue02"` [01-initial_stack_creation.log](https://github.com/user-attachments/files/16389923/01-initial_stack_creation.log) The second file is after adding a 3rd parameter: - `"Foo":...

The API response to `az automation schedule show` doesn't include the parameters 😒 ```bash az automation schedule show \ --automation-account-name $(pulumi stack output automation-account-name) \ --name $(pulumi stack output schedule-name)...

> I'm going to see if I can inspect and report on the parameters via the runbook Hmm, no. I can't do that. These parameters aren't exposed to the runbook....

OK, confirmed. The parameters are *definitely* not updated on changes. This is not a UI bug, I've confirmed with the `az rest` command. I exposed the `jobScheduleId` in my pulumi...

> Are we confident to say this is a limitation on the Azure side? Yes. That matches with all my testing, and `replaceOnChanges` doesn't negatively impact things.