chariott 0.2.1-pre-release

What's Changed

• Update notice file workflow by @ladatz in #261
• chore: Bump the dev-dependencies group with 2 updates by @dependabot in #263
• chore: Notice file change by @github-actions in #269
• Add multi and arm dockerfiles by @devkelley in #265
• Workflow and UID fixes by @ladatz in #272
• chore: Bump mio from 0.8.10 to 0.8.11 by @dependabot in #271

Full Changelog: 0.2.0...0.2.1

chariott 0.2.0 pre-release

Summary of release

This release consists of a POC for service discovery and intent brokering. Refer to the README.md and docs folder for more information.

At the top-level, there are two directories showing the two components "service_discovery" and "intent_brokering". Today, these are two separate components which work completely independently and are not integrated. This release includes some restructuring of the repository, and a rename from "chariott" (project name) to the functionality of each component. Therefore, paths and package names may need to be updated accordingly.

The dogmode demo scenario was moved out of this repository and into the chariott-example-applications repository, which will host these larger scenarios and allow for separation of the core functionality with large demo scenarios.

What's Changed

• Address devskim warnings by @ladatz in #196
• Remove v1 of the mobile net to resolve storage issues in workflows by @ladatz in #197
• Add GIT_LFS_SKIP_SMUDGE var to failing workflows by @devkelley in #203
• Update rust toolchain to 1.70 by @ladatz in #199
• chore: Notice file change by @github-actions in #204
• Fully qualify docker image registry by @ladatz in #217
• Fix typo in grpcurl commands in service discovery readme by @ladatz in #219
• chore: Bump the dev-dependencies group with 21 updates by @dependabot in #232
• chore: Notice file change by @github-actions in #233
• chore: Notice file change by @github-actions in #234
• chore: Bump the dev-dependencies group with 2 updates by @dependabot in #235
• chore: Notice file change by @github-actions in #240
• chore: Bump the dev-dependencies group with 8 updates by @dependabot in #241
• chore: Notice file change by @github-actions in #242
• chore: Notice file change by @github-actions in #243
• chore: Bump the dev-dependencies group with 4 updates by @dependabot in #248
• Restructure Chariott repo to show the separation between intent brokering and service discovery by @ladatz in #247
• chore: Notice file change by @github-actions in #249
• chore: Bump the dev-dependencies group with 2 updates by @dependabot in #250
• chore: Notice file change by @github-actions in #252
• Replace the project name "Chariott" in code and package names, with the component name "intent brokering" by @ladatz in #251
• chore: Bump the dev-dependencies group with 2 updates by @dependabot in #254
• chore: Notice file change by @github-actions in #255
• chore: Notice file change by @github-actions in #257
• chore: Bump the dev-dependencies group with 5 updates by @dependabot in #258
• Remove Dog Mode from Chariott repository now that it is in chariott-example-applications repository by @ladatz in #259

Full Changelog: 0.1.1...0.2.0

chariott 0.1.1 pre-release

This release contains Eclipse Chariott version 0.1.1. It is the first "pre-release" of the Chariott project. It consists of a POC for service discovery and intent brokering. Refer to the README.md and docs folder for more information.

Included in this are the Chariott streaming service, which uses the event subsystem to show a POC of streaming with the intent broker, enabling the "subscribe" intent.

At the top-level, there is also a directory called "service_discovery" which shows a service discovery system that is very simple to integrate with. This is the beginning of decoupling the service discovery system with other pluggable components that could be introduced later, like an intent broker or publish-subscribe functionality. At the heart of this system is the service registry, which applications can register themselves with. Other applications can then "discover" services based on their fully qualified name, or a logical grouping called "namespace".

Includes a few example applications:

• simple-provider for getting started with Chariott
• invoke-command sample demonstrating how to invoke a command in another service using Chariott's intent broker
• a series of example applications which come together to show the dogmode demo end-to-end use case
• simple discovery sample in the service_discovery directory