Skip to main content
Solved

Endpoint name and JSON body type error in the 'deployment automation' documentation


Hi

First off, I’m not sure where I was supposed to report this. There was a blog from 3 years ago (link) referring to an open source repository of the documentation on GitHub. However, this has since been archived and doesn’t indicate that it is being maintained anywhere else. Thus leaving me unable to open a simple pull request.

 

Now I’m here, where a relatively small improvement report like this doesn’t really fit the ‘Question’, ‘Conversation’, or ‘Idea’ categories. If there’s another/better way, let me know! 

 

When following the documentation on deployment automation, I’ve ran into some difficulties. These difficulties were mainly from the documentation being incorrect. I’m referring to the following page and section (markdown anchor included in url): https://docs.thinkwisesoftware.com/docs/sf/deployment_automation#automate-the-creation-of-a-deployment-package

The JSON snippet here indicates that the POST request endpoint to indicium is task_start_deployment_package. However, this should be start_deployment_package, without the ‘task_’ prefix. This should fix a 404 response to any documentation followers.

Next, the JSON body of the request has two incorrect types for two key/value pairs.

"upgrade_method": "0" is of type number, i.e. should be 0 in the example, without double quotes.
"verify": "1” is of type number, i.e. should be 1 in the example, without double quotes.


Finally, this should fix a 422/500 response to any documentation followers.
 

The most interesting finding to me was that a news blog from 6 months ago doesn’t have these errors: 


Kind regards,

Petar

Best answer by Mark Jongeling

Hi Petar,

Usually you can report these errors as a ticket in TCP but it is no problem to report it here. Thank you for noticing, I'll make sure it gets resolved. 

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

2 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3945 replies
  • Answer
  • August 17, 2022

Hi Petar,

Usually you can report these errors as a ticket in TCP but it is no problem to report it here. Thank you for noticing, I'll make sure it gets resolved. 

 


Forum|alt.badge.img+3

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings