As you can tell, in the good package, the last two curly brackets are there, in the bad one, the message is truncated and stops too early. Not sure why. From Postman I can send the message correctly and every json validator I have checked says it is a good json string. The main thing I also noticed, is that when the job runs, under the logs for the job, there is a new tab, Run Info. Under this tab there is a Request body field. The Web Service field has the two curly brackets there, but under this tab, the Run Info tab, they are missing. I am guessing that somewhere between parsing and send the message, Tidal drops the last two curly brackets.
New Cisco Champion Radio release on Cisco Intersight Cloud Operations PlatformListen: https://smarturl.it/CCRS8E15Follow us: https://twitter.com/CiscoChampion Known as Project Starship when it was introduced in June 2017, Cisco Intersight has come a ...
Join us live on Thursday, April 8 at 10 am PT (and on demand after) as we join Cisco and HashiCorp executives to discuss the importance of IaC automation, Intersight Service for Terraform, and how to better manage hybrid cloud infrastructure at scale...
Join us live on Thursday, April 8 at 10 am PT (and on demand after) where Cisco and HashiCorp executives will discuss the importance of IaC automation, Cisco Intersight Service for Hashicorp Terraform, and how to better manage hybrid cloud infrastructure...
How to START with Infrastructure as a code for Cisco Cloud Solutions
ACI Ansible Modules Documentation Guide
Cisco Collections on Ansible Galaxy
Cisco DevNet Learning Labs
DevNet Introduction to ACI and Ansible
DevNet Introduction to ACI a...