Skip to content

log,exec ws error handler, wasm runtime installation , OTA script, registery and catalog item deploy fix#211

Merged
emirhandurmus merged 10 commits into
eclipse-iofog:developfrom
Datasance:develop
Jun 30, 2026
Merged

log,exec ws error handler, wasm runtime installation , OTA script, registery and catalog item deploy fix#211
emirhandurmus merged 10 commits into
eclipse-iofog:developfrom
Datasance:develop

Conversation

@emirhandurmus

Copy link
Copy Markdown
Contributor

No description provided.

Resolve package.wasm artifacts on the operator machine, stage shims via
install_wasm_runtimes.sh, SCP binaries for airgap remotes, and register each
configured handler with edgelet deploy -f after wait_edgelet_ready.
Wire create, configure, delete, get auth-groups, and get auth-group NAME for
embedded Controller auth. Bump iofog-go-sdk to v3.8.0-rc.10 and operator to
v3.8.0-rc.2.
Use WithAPIVersion(util.GetCliApiVersion()) so Application, ApplicationTemplate,
Microservice, and NATS rule deploys target the correct CRD apiVersion.
…version

Port init-aware service stop and embedded-engine restart (containerd then
edgelet) so controller OTA does not leave cli/receipt ahead of the running
fat daemon. Gate bootstrap readiness on receipt vs daemon.version and fix
version field parsing for modern edgelet --version output.
Add shared registry helpers and upsert catalog items by name instead of
relying on YAML id. Emit numeric registry ids in get and describe output.
Update versions.mk, operator docs, and test fixtures to match the new
edgelet release.
Align sample YAML with current controller and edgelet images, agent names,
and local SSH endpoints used in manual testing.
@emirhandurmus emirhandurmus merged commit e66e3e3 into eclipse-iofog:develop Jun 30, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant