Skip to content

Commit 1fa5ef4

Browse files
committed
Update Blog “getting-started-with-the-redfish-api-part-2”
1 parent b82d0bd commit 1fa5ef4

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

content/blog/getting-started-with-the-redfish-api-part-2.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ tags:
1111
- redfish
1212
- iLO 5
1313
---
14+
### Updated July 25, 2023
15+
1416
# **A primer for coders**
1517

1618
In my last blog [post](/blog/getting-started-with-ilo-restful-api-redfish-api-conformance) I began a discussion about best practices for writing Redfish API client code. Last time we talked about resource versioning and resource inter-linking. I explained that client code should discover the data model and avoid making incorrect assumptions. In this post I will continue discussing some issues you should be aware of in order to create durable clients that interoperate across different implementations of the Redfish API.
@@ -33,4 +35,4 @@ We are often asked the question: “What version of Redfish does iLO support?
3335

3436
## What is next?
3537

36-
We hope we have given you enough information to get started with the iLO RESTful API and see the benefits of server automation from a single API. As we continue to improve and update our Redfish interface, please refer to our [documentation](https://hewlettpackard.github.io/ilo-rest-api-docs/ilo5/).
38+
We hope we have given you enough information to get started with the iLO RESTful API and see the benefits of server automation from a single API. As we continue to improve and update our Redfish interface, please refer to our [documentation](https://servermanagementportal.ext.hpe.com/).

0 commit comments

Comments
 (0)