libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From to...@apache.org
Subject [libcloud] 03/03: Update docs.
Date Sat, 11 Jul 2020 16:15:59 GMT
This is an automated email from the ASF dual-hosted git repository.

tomaz pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/libcloud.git

commit f122600d2adf181a9b100cdd552cd02979c5b1b9
Author: Tomaz Muraus <tomaz@tomaz.me>
AuthorDate: Sat Jul 11 18:15:47 2020 +0200

    Update docs.
---
 docs/compute/pricing.rst | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/docs/compute/pricing.rst b/docs/compute/pricing.rst
index 1511dd3..b9d7014 100644
--- a/docs/compute/pricing.rst
+++ b/docs/compute/pricing.rst
@@ -50,8 +50,15 @@ Pricing file data is available at the following locations:
 * https://libcloud-pricing-data.s3.amazonaws.com/pricing.json.sha256
 * https://libcloud-pricing-data.s3.amazonaws.com/pricing.json.sha512
 
-First file contains actual pricing JSON file and the second and third contain
-SHA 256 and SHA 512 sum of that file content.
+First file contains the actual pricing JSON file and the second and third
+contain SHA 256 and SHA 512 sum of that file content.
+
+We are providing this service free of charge so it's important that you don't
+abuse it. This means you should not download this file more than once per day
+(it makes no sense to do it more often, since it only gets updated once per
+day if there are any changes) and you should utilize one of the caching
+approaches described below and only download ``pricing.json`` file when there
+are any changes / updates.
 
 You can use the content of the sha sum files to implement efficient file
 downloads and only download pricing.json file if the content has changed.
@@ -62,7 +69,7 @@ downloading ``pricing.json`` file is the sha sum value has changed.
 An alternative to using the content of the sha sum file is caching the value
 of the ``ETag`` HTTP response header which you can retrieve by issuing HTTP
 ``HEAD`` request against the ``pricing.json`` URL. HEAD request will only
-return the object metdata without the actual content.
+return the object metadata without the actual content.
 
 For example:
 


Mime
View raw message