Core Updater Plugin
Exposes a messagebus API to check for and initiate core module updates. Update checks use GitHub releases or PyPI indices, depending on plugin configuration. The update command is configurable and is started in a new session. Note that the calling module might be killed during updates and in many cases, systemD will kill the update process if the parent service stops.
Configuration
The update command, core package, and update references are all configurable. For version checks, a valid Python Package must be installed and versions must either be published to PyPI or tagged as GitHub releases.
PHAL:
admin:
neon-phal-plugin-core-updater:
enabled: True
core_module: neon_core
github_ref: NeonGeckoCom/NeonCore
update_command: systemctl start update_service
Messagebus API
Messagebus events are handled to check for updates and to update to a newer version.
Check for updates
emitting:
msg_type: neon.core_updater.check_update
data:
include_prerelease: True
will generate the response:
msg_type: neon.core_updater.check_update.response
data:
new_version: <latest version including pre-releases/alphas>
installed_version: <current installed version>
github_ref: <plugin configured GH ref>
pypi_ref: <plugin configured PyPI ref>
If include_prereleases is not present in the request, the installed version is
used to determine if pre-releases should be included.
Note that only one of github_ref or pypi_ref should be configured. If both
are configured, PyPI checks take priority.
Start Updates
emitting:
msg_type: neon.core_updater.start_update
data:
version: <new_version>
will start the configured update command in a shell with version passed as the
first and only argument. If version is omitted, the configured update command
will be called with no commands.
Metadata
Release files for neon-phal-plugin-core-updater 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| neon-phal-plugin-core-updater-1.3.0.tar.gz | 5.6 kB | Without provenance | Details for neon-phal-plugin-core-updater-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neon_phal_plugin_core_updater-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for neon_phal_plugin_core_updater-1.3.0-py3-none-any.whl |
Total release size: 12.4 kB
Release files / neon-phal-plugin-core-updater-1.3.0.tar.gz
| Download URL | neon-phal-plugin-core-updater-1.3.0.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcc18832fe22d980cde9d5e2924bae0160834be2c4952961d056c5573381b8a2
|
|
BLAKE2b-256 checksum How to use checksums |
e72d2253789256cb4693fa6f9acc256a1dcae46ad031d9f3b41bad9d97955862
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / neon_phal_plugin_core_updater-1.3.0-py3-none-any.whl
| Download URL | neon_phal_plugin_core_updater-1.3.0-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1cec1ae50dcb12ce56b53ad53600ba47e039082b5de218318231664efe8adb9d
|
|
BLAKE2b-256 checksum How to use checksums |
a168625ff26986d694f66aeee2d97b7fd30da82b49879660a71d1c18a239d04b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for neon-phal-plugin-core-updater 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.