Only the Transactional API is deprecated and replaced by Query API

[renetapopova]

https://linear.app/neo4j/document/deprecated-http-api-201a92a94a71

[bigmontz]

For pages which are describing deprecated apis, it might be clear to add the deprecated badge in the page.

[NataliaIvakina]

I don't know why but in the preview there no 'Deprecated in 5.26' labels on the page level. You see only 'Not available on Aura'

[NataliaIvakina]

I might be wrong but it seems that page-role: not-on-aura in the publish and preview files overwrites "local" page-role on the pages

[NataliaIvakina]

Suggested change

	:page-role: deprecated-5.26
	[role=label--deprecated-5.26]

[renetapopova]

I might be wrong but it seems that page-role: not-on-aura in the publish and preview files overwrites "local" page-role on the pages

Yes, I thought that it might happen. I'll add it to the pages. Thanks

[neo4j-docops-agent]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

[stefano-ottolenghi]

I don't think this is helpful for users. The HTTP API is deprecated, and the whole of it. None of this manual documents clustering endpoints. The fact that you can still submit a GET request to localhost:7474 and get a list of endpoints doesn't make the HTTP API less deprecated. The same content (the Discovery API) is surfaced in the Query API manual so I don't think anybody is particularly confused by the state of things.

[bigmontz]

I don't think this is helpful for users. The HTTP API is deprecated, and the whole of it. None of this manual documents clustering endpoints. The fact that you can still submit a GET request to localhost:7474 and get a list of endpoints doesn't make the HTTP API less deprecated. The same content (the Discovery API) is surfaced in the Query API manual so I don't think anybody is particularly confused by the state of things.

Is there any documentation around the clustering endpoints? HTTP Api is kind of a broad term.

If we have docs pages with clustering endpoints and other non-deprecated endpoints, we can narrow down the introduction to mention that this docs only refers to run queries and transaction. Then point people for the other endpoints docs. In this case, we can simply add the global deprecation notice. Along with that, the clustering endpoint might need to be removed from the docs.

[NataliaIvakina]

I don't think this is helpful for users. The HTTP API is deprecated, and the whole of it. None of this manual documents clustering endpoints. The fact that you can still submit a GET request to localhost:7474 and get a list of endpoints doesn't make the HTTP API less deprecated. The same content (the Discovery API) is surfaced in the Query API manual so I don't think anybody is particularly confused by the state of things.

Is there any documentation around the clustering endpoints? HTTP Api is kind of a broad term.

If we have docs pages with clustering endpoints and other non-deprecated endpoints, we can narrow down the introduction to mention that this docs only refers to run queries and transaction. Then point people for the other endpoints docs. In this case, we can simply add the global deprecation notice. Along with that, the clustering endpoint might need to be removed from the docs.

Clustering endpoints are documented here - https://neo4j.com/docs/operations-manual/current/clustering/monitoring/endpoints/.

[NataliaIvakina]

Along with that, the clustering endpoint might need to be removed from the docs.

@bigmontz , do you mean that the clustering endpoints should be removed from this docset? But anyway they will remain in the Example responses, not only here but also in the Query API docs.

[bigmontz]

Along with that, the clustering endpoint might need to be removed from the docs.

@bigmontz , do you mean that the clustering endpoints should be removed from this docset? But anyway they will remain in the Example responses, not only here but also in the Query API docs.

Yes, than the document can be returned to the original and we just need to make clear the scope of the document and deprecation on the introduction page.

[renetapopova]

Along with that, the clustering endpoint might need to be removed from the docs.

@bigmontz , do you mean that the clustering endpoints should be removed from this docset? But anyway they will remain in the Example responses, not only here but also in the Query API docs.

Yes, than the document can be returned to the original and we just need to make clear the scope of the document and deprecation on the introduction page.

What about the Authorization header, the content type application/json, and the discovery API? Should I remove them as well?

[bigmontz]

Auth and application/json should keep on it, just with an notice that the auth-method itself is not deprecated since it is used in other places.

About the Discovery API, this a bit more complicated, since it doesn't have a place to go and the endpoint is not deprecated.

[renetapopova]

Replaced by #159