Highlights

Notification feature has been enhanced to support notifications for successful runs in addition to failed runs.

Example:

## optional - if specified exporter will send notifications on failure# supported notification services are:# - apprise (https://github.com/caronc/apprise)# omit/comment out section if not requirednotifications:# optional - apprise notification config# if used, required: specify one or more service_urls or a config_path# - if both are specified, config_path takes precedence# if service_urls is used, service_urls can also be specified as env var: APPRISE_URLS# - env var takes precedence over service_urls below if both specifiedapprise:service_urls:[]# - "json://localhost:8080/notify"config_path:""plugin_paths:[]storage_path:""custom_title:""custom_attachment_path:""on_success:falseon_failure:true

What's Changed

• 61 notification by@pchang388 in#67

Full Changelog:v1.6.0...v1.6.1

Contributors

Highlights

Notifications for failed runs are now possible via apprise. Users can specify in their yaml configuration to utilize this feature.

Example configuration:

## optional - if specified exporter will send notifications on failure# supported notification services are:# - apprise (https://github.com/caronc/apprise)# omit/comment out section if not requirednotifications:# optional - apprise notification config# if used, required: specify one or more service_urls or a config_path# - if both are specified, config_path takes precedence# if service_urls is used, service_urls can also be specified as env var: APPRISE_URLS# - env var takes precedence over service_urls below if both specifiedapprise:service_urls:      -"json://localhost:8080/notify"config_path:""plugin_paths:[]storage_path:""custom_title:""custom_attachment_path:""

Example uses JSON HTTP POST request for notification (https://github.com/caronc/apprise/wiki/Notify_Custom_JSON).

What's Changed

• 61 notification by@pchang388 in#66

Full Changelog:v1.5.0...v1.6.0

Contributors

Highlights

Potential breaking changes:

• assets.verify_ssl has been moved tohttp_config.verify_ssl and the default value has been updated tofalse.
• additional_headers has been moved tohttp_config.additional_headers

HTTP request configuration is now customizable by user and can override the defaults for the following properties:

• timeout:30
• backoff_factor:2.5
• retry_codes:[413, 429, 500, 502, 503, 504]
• retry_count:5

The default values for the HTTP request configuration are conservative and allow for enough time between retries for per minute rate limits to be refreshed. More information on retries and backoff_factor can be foundhere.

What's Changed

• fix missing github checkout step by@pchang388 in#58
• add helm option in docs by@pchang388 in#59
• fix position of doc addition by@pchang388 in#60
• Http input feature by@pchang388 in#62
• update configuration defaults and checks by@pchang388 in#63
• update configuration options and descriptions for http_config changes by@pchang388 in#64

Full Changelog:v1.4.1...v1.5.0

Contributors

What's Changed

• update full example and build commands by@pchang388 in#55
• update description on application mode by@pchang388 in#56
• Change back off retry behavior by@pchang388 in#57

Full Changelog:v1.4.0...v1.4.1

Contributors

Highlights

• Addrun_interval setting to allow very basic scheduling. The exporter will operate as an always running application if specified.
  • Optional property: specify a time inseconds for the exporter to wait in between subsequent runs.
  • Setting this0 (default) or omitting it from the configuration will execute a single run and exit.
• Add docker-compose example for always running application use case.

What's Changed

• 53 schedule by@pchang388 in#54

Full Changelog:v1.3.1...v1.4.0

Contributors

What's Changed

• update readme for assest skip feature by@pchang388 in#48
• create user provided output_path directory if not exists by@pchang388 in#49
• make create output_path dir error catchable to allow for docker usage by@pchang388 in#50
• minor fix on logging and output description by@pchang388 in#51
• fix minor spacing issue on log message by@pchang388 in#52

Full Changelog:v1.3.0...v1.3.1

Contributors

Highlights

• Python version bumped to3.13.0
• All dependencies bumped to respective latest versions
• If an API call to get an image/attachment or its metadata fails, the exporter will skip the asset and log the error. If usingassets.modify_markdown option, the asset links in the document will be untouched and in its original form. All API calls are retried 3 times after initial failure.

What's Changed

• Attempt to add logic to skip an image/attachment if API call fails by@pchang388 in#46

Full Changelog:v1.2.0...v1.3.0

Contributors

What's Changed

• Update doc brief by@pchang388 in#40
• update readme for suggestion by@intrepidsilence by@pchang388 in#41
• bump python version to 3.12.4, update pkg depedencies to latest by@pchang388 in#42

Full Changelog:v1.1.0...v1.2.0

Contributors

New Features

• Attachments can now be exported and placed in their respectiveattachments/{page}/ directory
• Docker Image Tagging changes to better facilitate testing and GitHub actions
• arm64 docker image support

Highlights

• Reworked Asset (Image/Attachment) archiver modules for better reusability and readability

What's Changed

• add arm64 docker image support by@pchang388 in#34
• Rework for attachments by@pchang388 in#36
• fix dockerfile image tag by@pchang388 in#37
• fix dockerfile image args by@pchang388 in#38
• fix release tag versioning for docker by@pchang388 in#39

Full Changelog:v1.0.2...v1.1.0

Contributors

What's Changed

• update readme by@pchang388 in#29
• fixes#30 raised by@Snaptraks by@pchang388 in#32

Full Changelog:v1.0.1...v1.0.2

Contributors