-
Notifications
You must be signed in to change notification settings - Fork 5
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
nextstagepropertiesjson Parameter could not be deserialized #3
Comments
Hi, @disbenovi! Can you please share the values that were passed to the Input Parameters? See example below |
In text - [ |
I am not seeing anything obviously wrong or prone to failure. Allow me some time to try to reproduce your issue. I'll return to you with the results soon. |
Appreciate it :) |
I was able to reproduce this issue. There was a change in a recent version of the Don't forget to increase the stages offsets, because they refer to the date of the latest run of the maintenance configuration and if you keep 1-2 days offsets, the resulting date will be in the past and the deployment will fail. If the runbook still fails for the same reason, please reopen the issue. |
Works now, thanks a lot for the prompt responses @helderpinto! |
Hello
Followed all the instructions, the automation account Managed Identity has the correct permissions on the Sub level.
When passing the nextstagepropertoesjson parameter on the runbook, an exception is thrown out:
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 7:10:52 PM - Error: Code=InvalidRequestContent; Message=The request content was invalid and could not be deserialized: 'Unexpected initial token 'String' when populating object. Expected JSON object or array. Path 'properties.template.resources.CliXml', line 7, position 6847.'.
The output seems to show that the parameters do get converted and read as the output shows the stagename :
However it just abruptly stops, and throws the exception.
The runtime environment is 5.1 for the Az modules, and the Powershell runbook.
The text was updated successfully, but these errors were encountered: