# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## 0.20.0 (2024-09-28) ### Chore - Switch to using oci feature - fix clippy lints - set missing link log to warn - Make wasmcloud host heartbeat interval configurable - update component/runtime/host crate READMEs - clarify missing secret config error - fix clippy lint - update secrets integration to use the update config structure Update the secrets integration in a wasmCloud host to include information about the policy that determines which backend to communicate with. This is a change that comes in from wadm where the policy block now contains the information about which backend to use. This also passes any propertes defined on the policy to the correct backend, which are stored as a versioned string-encoded JSON object. - enable `ring` feature for `async-nats` - address clippy warnings - update to stream-based serving - improve error messages for missing links When known interfaces are accessed, we show a message that notes that the target is unknown, but we can improve on that by alerting the user to a possibly missing link. - improve error messages for missing links When known interfaces are accessed, we show a message that notes that the target is unknown, but we can improve on that by alerting the user to a possibly missing link. - downgrade link/claims log/trace - Replace actor references by component in crates Rename wash-cli wash-build tests name and references Fix nix flake path to Cargo.lock file Fix format Rename in wash-cli tests - Bump oci-distribution to 0.11.0 - generate changelogs after 1.0.1 release - updated with newest features - replace references to 'actor' with 'component' - remove unnecessary todo comments - show provider ID on healthcheck failure messages - improve error message for forceful provider shutdown - update URLs to `wrpc` org - address clippy warnings - Bumps host version to rc.2 While I was here, I fixed the issue where we were using the host crate version instead of the top level binary host version in our events and ctl API responses - imrpove wording for spec/provider ref mismatch This commit slightly improves the wording when a provider ID and component specification URL mismatch occurs, along with specifying a possible solution. This error is thrown by `wash` and it's a bit difficult to figure out what to resolve it otherwise. - update `messaging` to `0.2.0` - remove compat crate - address clippy warnings - use `&str` directly - Use traces instead of tracing user-facing language to align with OTEL signal names - refactor component invocation tracking - remove functionality related to wasmbus invocations - update wRPC - revert incorrectly handled config conficts - remove plural actor events - integrate set-link-name and wrpc - remove unused imports/functions - remove unused function - reintroduce wasmbus over wrpc - fix `wasmcloud-host` clippy warning - update version to 0.82.0 - implement preview 2 interfaces - bump wasmcloud to 0.81 - use consistent message prefix - address clippy issue This is caused by Rust update - remove `local` host - remove support for bindle references - polish tracing and logging levels - disambiguate traced function names - improve reference parsing - add logs related to registry config - add some control interface logs - resolve 1.73.0 warnings - give NATS 2 secs to start in test - rename SUCCESS to ACCEPTED, None concurrent max - drop logging level to trace - reduce verbosity of instrumented functions - satisfy clippy linting - emit more clear start message - reduce noise from REFMAP entries - reduce noise on instruments - remove noisy fields from instruments - rename friendly noun - refactor connection opts - made fetch arg ordering consistent ### Documentation - add README for the host crate ### New Features - Adds support for batch support to the host This enables keyvalue batch support inside of the host, along with a test to make sure it works. Not all of our providers implement batch yet, so this uses the Redis provider, which did have implementions. I did have to fix the redis provider to get the right type of data back and transform it. I also had to update our wRPC versions so we could pick up on some bug fixes for the types we are encoding in the batch interface. - fallback to `wrpc:blobstore@0.1.0` - support for sending out config updates to providers - add Host level configurability for max_execution_time by flag and env variables - Introduce humantime::Duration for capturing human readable input time. - Add the `--max-execution-time` flag (alias: --max-time) to wasmcloud binary and wash up command, allowing for configuration of the max execution time for the Host runtime. - Set Default to 10min and Time format to Milliseconds. - Add support for supplying additional CA certificates to OCI and OpenTelemetry clients - fetch secrets for providers and links - add secrets handler impl for strings - set NATS queue group - conflate `wasi:blobstore/container` interface with `blobstore` - pass original component instance through the context - upgrade `wrpc`, `async-nats`, `wasmtime` - support ScaleComponentCommand w/ update - allow empty payloads to trigger stop_host - add link name to wRPC invocations This commit adds the "link-name" header to invocations performed by the host using wRPC. - Add support for configuring grpc protocol with opentelemetry - Updates host to support new wasm artifact type This change is entirely backwards compatible as it still supports the old artifact type. I did test that this can download old and new manifest types - gracefully shutdown epoch interrupt thread - generate crate changelogs - count epoch in a separate OS thread - handle invocations in tasks - propagate `max_execution_time` to the runtime - limit max execution time to 10 minutes - update to Wasmtime 20 - update `wrpc:keyvalue` in providers part of this process is adopting `wit-bindgen-wrpc` in the host - update `wasi:keyvalue` - switch to `wit-bindgen-wrpc` - add label_changed event for label update/delete This commit adds a `label_changed` event that can be listened to in order to be notified of label changes on a host. The single event handles both updates and deletes. - use native TLS roots along webpki - fetch configuration direct from bucket - implement `wrpc:blobstore/blobstore` for FS - implement Redis `wrpc:keyvalue/{atomic,eventual}` - implement `wasi:http/outgoing-handler` provider - deliver full config with link - Add flags for overriding the default OpenTelemetry endpoint - Switch to using --enable-observability and --enable- flags - support pubsub on wRPC subjects Up until now, publishing and subscribing for RPC communcations on the NATS cluster happened on subjects that were related to the wasmbus protocol (i.e. 'wasmbus.rpc.*'). To support the WIT-native invocations, i.e. wRPC (#1389), we must change the publication and subscription subjects to include also the subjects that are expected to be used by wprc. This commit updates the provider-sdk to listen *additionally* to subjects that are required/used by wrpc, though we do not yet have an implementation for encode/deocde. - include actor_id on scaled events - downgrade provider claims to optional metadata - downgrade actor claims to optional metadata - Glues in named config to actors This introduces a new config bundle that can watch for config changes. There is probably a way to reduce the number of allocations here, but it is good enough for now. Also, sorry for the new file. I renamed `config.rs` to `host_config.rs` so I could reuse the `config.rs` file, but I forgot to git mv. So that file hasn't changed - implement AcceptorWithHeaders - implement wasmcloud_transport wrappers - implement `wrpc:http/incoming-handler` - begin incoming wRPC invocation implementation - switch to `wrpc` for `wasmcloud:messaging` - switch to `wrpc:{keyvalue,blobstore}` - implement `wrpc:http/outgoing-handler.handle` - support component invoking polyfilled functions - change set-target to set-link-name Up until the relatively low-level `wasmcloud:bus/lattice` WIT interface has used a function called `set-target` to aim invocations that occurred in compliant actors and providers. Since wRPC (#1389) enabled wasmCloud 1.0 is going to be WIT-first going forward, all WIT-driven function executions have access to the relevant interface (WIT interfaces, rather than Smithy-derived ones) that they call, at call time. Given that actor & provider side function executions have access to their WIT interfaces (ex. `wasi:keyvalue/readwrite.get`), what we need to do is differentiate between the case where *multiple targets* might be responding to the same WIT interface-backed invocations. Unlike before, `set-target` only needs to really differentiate between *link names*. This commit updates `set-target` to perform differentiate between link names, building on the work already done to introduce more opaque targeting via Component IDs. - remove module support - add invocation and error counts for actor invocations Add two new metrics for actors: * the count of the number of invocations (`wasmcloud_host.actor.invocations`) * the count of errors (`wasmcloud_host.actor.invocation.errors`) This also adds a bunch of new attributes to the existing actor metrics so that they make sense in an environment with multiple hosts. Specifically this adds: * the lattice ID * the host ID * provider information if a provider invoked the actor: ** the contract ID ** the provider ID ** the name of the linkdef For actor to actor calls, instead of having the provider metadata it instead has the public key of the invoking actor. An example of what this looks like as an exported Prometheus metric: ``` wasmcloud_host_actor_invocations_total{actor_ref="wasmcloud.azurecr.io/echo:0.3.8", caller_provider_contract_id="wasmcloud:httpserver", caller_provider_id="VAG3QITQQ2ODAOWB5TTQSDJ53XK3SHBEIFNK4AYJ5RKAX2UNSCAPHA5M", caller_provider_link_name="default", host="ND7L3RZ6NLYJGN25E6DKYS665ITWXAPXZXGZXLCUQEDDU65RB5TVUHEN", job="wasmcloud-host", lattice="default", operation="HttpServer.HandleRequest"} ``` Provider metrics will likely need to wait until the wRPC work is finished. - Add initial support for metrics - remove requirement for actors to have capabilities in claims - add event name as suffix on event topic - enable updating host labels via the control interface - Adds some additional context around test failures I was seeing - Adds support for actor config This is a fairly large PR because it is adding several new control interface topics as well as actually adding the actor config feature. This feature was motivated by 2 major reasons: 1. We have been needing something like this for a while, at the very least for being able to configure link names in an actor at runtime 2. There aren't currently any active (yes there were some in the past) efforts to add a generic `wasi:cloud/guest-config` interface that can allow any host to provide config values to a component. I want to use this as a springboard for the conversation in wasi-cloud as we will start to use it and can give active feedback as to how the interface should be shaped With that said, note that this is only going to be added for actors built against the component model. Since this is net new functionality, I didn't think it was worth it to try to backport. As for testing, I have tested that an actor can import the functions and get the values via the various e2e tests and also manually validated that all of the new topics work. - implement wasifills for simple types - implement outgoing HTTP - handle ctl requests concurrently - parse labels from args - support annotation filters for stop/scale - publish periodic provider health status - implement `wasi:logging` for actors - ignore `stop_provider` annotations - support policy service - add support for call aliases - support chunking and dechunking of requests - implement `wasi:blobstore` - support OTEL traces end-to-end - send OTEL config via HostData - add support for putting registry credentials via control interface - support registry settings via config service and command-line flags - partially implement `wasi:keyvalue/atomic` - implement `wasmcloud:http/incoming-handler` support - delete claims when actors or providers are stopped - remove actor links on deletion - implement link names and a2a calls - fill in missing data in host pings and heartbeat messages - implement ctl_topic_prefix - add claims and link query functionality - introduce `wasmcloud-compat` crate - generate host name based on a random number - add support for non-default link names - add support for custom lattice prefix - implement `wasmcloud:messaging/consumer` support - implement `wasi:keyvalue/readwrite` support - handle launch commands concurrently - implement actor -> provider linking - implement update actor - implement linkdef add/delete - implement start and stop provider commands - implement actor operations - implement inventory - implement host stop - implement host ping - apply labels from environment - introduce wasmbus lattice - implement data streaming - make claims optional (at least for now) - add streaming support to `wasmcloud:bus` - rename `wasmcloud_host` -> `wasmcloud_runtime` - remove all `wasmcloud-interface-*` usages - add support for `command` executables (I/O actors) - add local lattice proving the concept, which is used for testing of the feature - implement an actor instance pool - implement builtin capabilities via WIT ### Bug Fixes - rework `wasi:http` error handling - log handling errors - Sets a higher value for the incoming events channel If you were running a high number of concurrent component invocations, it would result in a warning (and possible hang/dropped message) due to a full channel. This change attempts to set the channel size to the `max_instances` value with a minimum and a maximum possible value (i.e we don't want something with 20k instances to have a channel that large). - remove provider caching for local file references This commit removes provider caching for local file references -- when a file is loaded via a container registry, caching is enabled but if it is loaded via a local file on disk, caching is never employed. - prevent Provider ConfigBundle early drop, do cleanup - always publish component_scale event - pass policy string directly to backend - use name instead of key for secret map - skip backwards-compat link with secret - check provided secrets topic for non-empty - setup debug traces This commit contains experimental code used to debug/replicate the o11y traces for making a call with http-client & http-provider. Running this requires the following hackery: - running the docker compose for o11y - (re) building dog-fetcher - modifying the WADM w/ dog fetcher (done by this commit) - build & create PAR for http-client - build & create PAR for http-server - set WASMCLOUD_OVERRIDE_TRACES_ENDPOINT before `wash up` - replacing existing wasmcloud host (in `~/.wash/downloads/v1.0.2`) - propagate traces through components - handle invocation handling errors - remove publish_event from stop_actor - differentiate no config and config error - allow overwriting provider reference - warn scaling with different imageref - rename scaled ID from actor to component - Don't clone targets with handlers This is a fix that ensures each component has its own set of link name targets. Before this, it was sharing the whole set of link names between all running component instances (of each individual component). - deliver target links to started provider - fix `link_name` functionality, reorganize tests - correct name and data streaming, update WIT - Recreates polyfill imports on update This fixes an issue where if you add a new custom interface to an actor when updating it, it would fail to have the imports in place - fix deadlock and slow ack of update - flatten claims response payload - race condition with initial config get - improve target lookup error handling - update wrpc_client - re-tag request type enum policy - instrument handle_invocation and call - Fixes write lock issue on policy service Our policy decision logic was taking a write lock even when reading the queue. This basically treated it like a mutex and slowed down the number of requests we could handle. - encode custom parameters as tuples - correctly invoke custom functions - bindgen issues preventing builds This commit fixes the provider bindgen issues for non http-server builds (ex. kv-redis) - set log_level for providers - fix clippy warning, added ; for consistency, return directly the instance instead of wrapping the instance's components in a future - Add comments, remove useless future::ready - fmt - add subject to control interface logs - publish claims with actor_scaled - override previous call alias on clash - update format for serialized claims - disable handle_links trace until wadm sends fewer requests - queue subscribe to linkdefs and get topics - drop problematic write lock - publish correct number of actor events - stop sending linkdef events on startup - change expected host label prefix to remove collision with WASMCLOUD_HOST_SEED - fixes #746 - return an InvocationResponse when failing to decode an invocation - deprecate HOST_ label prefix in favor of WASMCLOUD_HOST_ - download actor to scale in task - proxy RUST_LOG to providers - rework host shutdown - Always include a timeout for graceful shutdown (e.g. if NATS connection dies, it will never finish) - Stop if one of the core wasmbus tasks dies - Flush NATS queues concurrently on shutdown - Handle `stopped` method errors - enforce unique image references for actors - properly format actors_started claims - Flushes clients when responding to ctl requests In cases where wadm was fairly busy, we started getting errors that the host wasn't acking our scale actor commands (even though it was actually scaling). So I added in some flushing when we send responses so we can be sure that the response actually got sent - proxy SYSTEMROOT to providers on Windows - use named fields when publishing link definitions to providers - allow namespaces with slashes - look for invocation responses from providers - store claims on fetch - clean-up imports - expose registry as a public module - attach traces on inbound and outbound messages Parse headers from CTL interface and RPC messages, and publish tracing headers on CTL and RPC responses - Flushes NATS clients on host stop Without this, sending responses to things like a host stop command or publishing the host stop event can fail as we don't ensure all messages in the NATS client queue have been sent - unwrap expired - handle stored claims without config_schema - return invocation responses for host failures - pub the context mod only with the otel feature enabled - use cached links for queries - remove redundant claim clone - always include cluster key as a valid issuer - pass OTEL settings to providers via deprecated env vars - ignore empty responses - store typed keys, not strings - properly handle empty responses - do not proxy env vars from host to providers - Matches up base64 encoding to what providers expected ### Other - add links integration test - bump for test-util release Bump wasmcloud-core v0.8.0, opentelemetry-nats v0.1.1, provider-archive v0.12.0, wasmcloud-runtime v0.3.0, wasmcloud-secrets-types v0.3.0, wasmcloud-secrets-client v0.3.0, wasmcloud-tracing v0.6.0, wasmcloud-host v0.82.0, wasmcloud-test-util v0.12.0, safety bump 8 crates SAFETY BUMP: wasmcloud-runtime v0.3.0, wasmcloud-secrets-client v0.3.0, wasmcloud-tracing v0.6.0, wasmcloud-host v0.82.0, wasmcloud-test-util v0.12.0, wasmcloud-provider-sdk v0.7.0, wash-cli v0.30.0, wash-lib v0.23.0 - add secrecy - fix outdated `ctl_seed` reference - document invocation handling failures - check component update ref and respond with a message before task - check component image reference on component update - expect stop_actor function parameter host_id to be unused - update `wrpc-interface-http` - update wRPC - update wRPC - update to wasmtime 17 - 'upstream/main' into `merge/wash` - bump crate versions - bump to `0.79.0` - update dependencies - bump version to `0.78.0` - update dependencies - remove `wit-deps` build scripts - update WIT dependencies - update dependencies - update `preview2-prototyping` ### Refactor - remove missing caching code - remove unused deps - move functionality into core This commit moves functionality that was previously located in the unreleased `wasmcloud-host` crate into core. - abort health check tasks on provider drop - include name with secret config - move SecretConfig into crate - address feedback, application name optional - collapse application field - efficiency, pass optional vec secrets - improve error representations, cleanup - light refactor from followup - remove extra trace_level field - improve error handling - improve error usage of bail - remove redundant handler clone - Actor -> Component - move wasmcloud wrpc transport client to core This commit moves the wasmcloud-specific wrpc transport client to the `wasmcloud-core` crate. From here, it can be used by both the host (`wasmbus`) and other places like tests. - move label parsing out of host library - remove deprecated code related to start actor cmd - rename label to key - drop write locks immediately - remove unnecessary mut - remove instance pooling - implement `ResourceRef::authority` - introduce artifact fetchers - derive `Default` for `Auth` - rename `RegistrySettings` -> `RegistryConfig` - rework fetching logic - be explicit about `async_nats` imports - reduce verbosity on actor logs - flatten optional annotations to always be set - construct a strongly typed HostData to send to providers - establish NATS connections concurrently - use `wasmcloud-compat` structs - remove unnecessary allocations - create bucket explicitly instead of stream This also gracefully handles errors where the bucket has already been provisioned with custom settings, allowing multiple hosts to run in the same pre-provisioned lattice - exclude self from instruments - use `wasmcloud-control-interface` - expand parameter names - remove `wasmbus-rpc` usage ### Style - comment - address nits - use skip_all - replace needs_chunking function with direct comparison - move longer fields to their own lines - update imports - satisfy clippy - stop unnecessarily satisfying clippy - remove constants - rename most instances of lattice and wasmbus to host - use context ### Chore (BREAKING) - update host w/ new ctrl iface - remove cluster_seed/cluster_issuers - rename ctl actor to component - update ctl to 0.31.0 ### New Features (BREAKING) - introduce linkdef_set_failed event - allow tuning runtime parameters - encrypt link secrets, generate xkeys for providers - configure observability with trace_level option - add secrets backend topic flag - Removes old guest config and uses runtime config instead Most of the changes are related to wit updates, but this removes the guest config from `wasmcloud:bus` and pulls down `wasi:config` in its place - rename actor_scale* events - remove capabilities - Adds version to control API This should be the final breaking change of the API and it will require a two phased rollout. I'll need to cut new core and host versions first and then update wash to use the new host for tests. - convert to `wrpc:blobstore` - use `wasmcloud:messaging` in providers Also implement statically invoking the `handler` on components in the host - start providers with named config - refactor componentspec, deliver links to providers - cache request by unique data - formalize policy service - wrap all ctl operations in CtlResponse - remove collection type aliases - flatten instances on actor/providers - fully support interface links, remove aliases - support wrpc component exports - support interface link put, component spec - Changes config topic to be for named config This is the first in a set of changes to move over to named config. It is not technically complete as you essentially have to name your config the same as the actor ID. I did this purposefully so as to not have a PR of doom with all the changes. The next PR will be adding named config to the scale command, then support for named config and providers in another PR after that - Updates topics to the new standard This is a wide ranging PR that changes all the topics as described in #1108. This also involved removing the start and stop actor operations. While I was in different parts of the code I did some small "campfire rule" cleanups mostly of clippy lints and removal of clippy pedant mode. - add heartbeat fields to inventory - change heartbeat payload to inventory - remove singular actor events, add actor_scaled - upgrade max_instances to u32 - rename max-concurrent to max-instances, simplify scale - use max concurrency instead of count - validate invocations for antiforgery and claims - implement provider health checks - implement structured logging - respect allow_file_load - enforce rpc_timeout - implement rpc,ctl,prov_rpc connections - use allow_latest and allowed_insecure config - use js_domain provided by cli - implement graceful provider shutdown delay - maintain cluster issuers list ### Bug Fixes (BREAKING) - ensure links are unique on source+interface+name - consistent host operations - remove support for prov_rpc NATS connection ### Refactor (BREAKING) - remove functionality from host (moved to core) - use result for changed() - rename lattice prefix to just lattice - make content_length a required field ### Commit Statistics - 374 commits contributed to the release over the course of 521 calendar days. - 1233 days passed between releases. - 369 commits were understood as [conventional](https://www.conventionalcommits.org). - 0 issues like '(#ID)' were seen in commit messages ### Commit Details
view details * **Uncategorized** - Update host w/ new ctrl iface ([`f418ad9`](https://github.com/wasmCloud/wasmCloud/commit/f418ad9c826e6ed6661175cf883882a37d5af1eb)) - Rework `wasi:http` error handling ([`4da0105`](https://github.com/wasmCloud/wasmCloud/commit/4da0105ac7bf463eeb79bc3047cb5e92664f8a7c)) - Log handling errors ([`726dd68`](https://github.com/wasmCloud/wasmCloud/commit/726dd689e6d64eb44930834425d69f21cefc61cd)) - Switch to using oci feature ([`fbd1dd1`](https://github.com/wasmCloud/wasmCloud/commit/fbd1dd10a7c92a40a69c21b2cbba21c07ae8e893)) - Sets a higher value for the incoming events channel ([`fc131ed`](https://github.com/wasmCloud/wasmCloud/commit/fc131edff75a7240fe519d8bbc4b08ac31d9bf1c)) - Fix clippy lints ([`fa01304`](https://github.com/wasmCloud/wasmCloud/commit/fa01304b62e349be3ac3cf00aa43c2f5ead93dd5)) - Remove missing caching code ([`d511d74`](https://github.com/wasmCloud/wasmCloud/commit/d511d74c21ab96f5913f5546e8253f34c73642a1)) - Remove unused deps ([`ac18892`](https://github.com/wasmCloud/wasmCloud/commit/ac188921856c9b5fe669531e309f3f416d1bb757)) - Remove functionality from host (moved to core) ([`47775f0`](https://github.com/wasmCloud/wasmCloud/commit/47775f0da33b36f9b2707df63c416a4edc51caf6)) - Move functionality into core ([`0547e3a`](https://github.com/wasmCloud/wasmCloud/commit/0547e3a429059b15ec969a0fa36d7823a6b7331f)) - Adds support for batch support to the host ([`8575f73`](https://github.com/wasmCloud/wasmCloud/commit/8575f732df33ca973ff340fc3e4bc7fbfeaf89f3)) - Remove provider caching for local file references ([`991cb21`](https://github.com/wasmCloud/wasmCloud/commit/991cb21d5bceee681c613b314a9d2dfaeee890ee)) - Add links integration test ([`9ac2e29`](https://github.com/wasmCloud/wasmCloud/commit/9ac2e29babcaa3e9789c42d05d9d3ad4ccd5fcc7)) - Ensure links are unique on source+interface+name ([`8db14d3`](https://github.com/wasmCloud/wasmCloud/commit/8db14d3bb320e6732c62c3abfe936d72e45fe734)) - Set missing link log to warn ([`d21d2a9`](https://github.com/wasmCloud/wasmCloud/commit/d21d2a9e7dffd16315eeb565e2cd0e1f1aeeac6c)) - Fallback to `wrpc:blobstore@0.1.0` ([`26d7f64`](https://github.com/wasmCloud/wasmCloud/commit/26d7f64659dbf3263f36da92df89003c579077cc)) - Introduce linkdef_set_failed event ([`be7233e`](https://github.com/wasmCloud/wasmCloud/commit/be7233e730dce14578651a17d16410d7a7dbe91c)) - Abort health check tasks on provider drop ([`47e80cf`](https://github.com/wasmCloud/wasmCloud/commit/47e80cf949a2cb287be479653336def31c130ba2)) - Use result for changed() ([`1931aba`](https://github.com/wasmCloud/wasmCloud/commit/1931aba6d2bf46967eb6f7b66fdffde96a10ae4d)) - Prevent Provider ConfigBundle early drop, do cleanup ([`77b1af9`](https://github.com/wasmCloud/wasmCloud/commit/77b1af98c1cdfdb5425a590856c0e27f2a7e805f)) - Support for sending out config updates to providers ([`6164132`](https://github.com/wasmCloud/wasmCloud/commit/61641322dec02dd835e81b51de72cbd1007d13cf)) - Allow tuning runtime parameters ([`f4b4eeb`](https://github.com/wasmCloud/wasmCloud/commit/f4b4eeb64a6eab4f6dfb540eacd7e2256d80aa71)) - Make wasmcloud host heartbeat interval configurable ([`40e5edf`](https://github.com/wasmCloud/wasmCloud/commit/40e5edfc0ee48fadccd0f0fb8f8d0eb53db026f0)) - Always publish component_scale event ([`76265cd`](https://github.com/wasmCloud/wasmCloud/commit/76265cdcbf2959f87961340576e71e085f1f4942)) - Update component/runtime/host crate READMEs ([`51c8ceb`](https://github.com/wasmCloud/wasmCloud/commit/51c8ceb895b0069af9671e895b9f1ecb841ea6c3)) - Bump for test-util release ([`7cd2e71`](https://github.com/wasmCloud/wasmCloud/commit/7cd2e71cb82c1e1b75d0c89bd5bda343016e75f4)) - Clarify missing secret config error ([`da461ed`](https://github.com/wasmCloud/wasmCloud/commit/da461edd4e5ede0220cb9923b1d9a62808f560dc)) - Fix clippy lint ([`f36471d`](https://github.com/wasmCloud/wasmCloud/commit/f36471d7620fd66ff642518ae96188fef6fde5e0)) - Include name with secret config ([`c666ef5`](https://github.com/wasmCloud/wasmCloud/commit/c666ef50fecc1ee248bf78d486a915ee077e3b4a)) - Move SecretConfig into crate ([`2ea22a2`](https://github.com/wasmCloud/wasmCloud/commit/2ea22a28ca9fd1838fc03451f33d75690fc28f2a)) - Address feedback, application name optional ([`b56982f`](https://github.com/wasmCloud/wasmCloud/commit/b56982f437209ecaff4fa6946f8fe4c3068a62cd)) - Collapse application field ([`388662a`](https://github.com/wasmCloud/wasmCloud/commit/388662a482442df3f74dfe8f9559fc4c07cedbe5)) - Pass policy string directly to backend ([`2695ad3`](https://github.com/wasmCloud/wasmCloud/commit/2695ad38f3338567de06f6a7ebc719a9421db7eb)) - Use name instead of key for secret map ([`1914c34`](https://github.com/wasmCloud/wasmCloud/commit/1914c34317b673f3b7208863ba107c579700a133)) - Update secrets integration to use the update config structure ([`da879d3`](https://github.com/wasmCloud/wasmCloud/commit/da879d3e50d32fe1c09edcf2b58cb2db9c9e2661)) - Skip backwards-compat link with secret ([`5506c8b`](https://github.com/wasmCloud/wasmCloud/commit/5506c8b6eb78d8e4b793748072c4f026a4ed1863)) - Efficiency, pass optional vec secrets ([`cfbf232`](https://github.com/wasmCloud/wasmCloud/commit/cfbf23226f34f3e7245a5d36cd7bb15e1796850c)) - Improve error representations, cleanup ([`d8ad437`](https://github.com/wasmCloud/wasmCloud/commit/d8ad4376cb4db282047de8c4f62f6b8b907c9356)) - Encrypt link secrets, generate xkeys for providers ([`d9281e2`](https://github.com/wasmCloud/wasmCloud/commit/d9281e2d54ac72e94f9afb61b3167690fe1fd89b)) - Add Host level configurability for max_execution_time by flag and env variables ([`a570a35`](https://github.com/wasmCloud/wasmCloud/commit/a570a3565e129fc13b437327eb1ba18835c69f57)) - Light refactor from followup ([`f354008`](https://github.com/wasmCloud/wasmCloud/commit/f354008c318f49565eb023a91cd3a3781d73c36a)) - Remove extra trace_level field ([`4e1d6da`](https://github.com/wasmCloud/wasmCloud/commit/4e1d6da189ff49790d876cd244aed89114efba98)) - Configure observability with trace_level option ([`2378057`](https://github.com/wasmCloud/wasmCloud/commit/2378057bbbabbfa5a2159b6621d6009396411dd7)) - Add support for supplying additional CA certificates to OCI and OpenTelemetry clients ([`24e77b7`](https://github.com/wasmCloud/wasmCloud/commit/24e77b7f1f29580ca348a758302cdc6e75cc3afd)) - Improve error handling ([`7f4cd4c`](https://github.com/wasmCloud/wasmCloud/commit/7f4cd4cf5da514bb1d10c9d064bb905de8621d8e)) - Check provided secrets topic for non-empty ([`5c68c89`](https://github.com/wasmCloud/wasmCloud/commit/5c68c898f8bd8351f5d16226480fbbe726efc163)) - Improve error usage of bail ([`c30bf33`](https://github.com/wasmCloud/wasmCloud/commit/c30bf33f754c15122ead7f041b7d3e063dd1db33)) - Fetch secrets for providers and links ([`e0324d6`](https://github.com/wasmCloud/wasmCloud/commit/e0324d66e49be015b7b231626bc3b619d9374c91)) - Add secrets handler impl for strings ([`773780c`](https://github.com/wasmCloud/wasmCloud/commit/773780c59dc9af93b51abdf90a4f948ff2efb326)) - Add secrecy ([`c71f153`](https://github.com/wasmCloud/wasmCloud/commit/c71f153b84e4ac4f84bdb934c9f7ca735eddd482)) - Add secrets backend topic flag ([`98b3986`](https://github.com/wasmCloud/wasmCloud/commit/98b3986aca562d7f5439d3618d1eaf70f1b7e75a)) - Set NATS queue group ([`c2bb9cb`](https://github.com/wasmCloud/wasmCloud/commit/c2bb9cb5e2ba1c6b055f6726e86ffc95dab90d2c)) - Fix outdated `ctl_seed` reference ([`5225b19`](https://github.com/wasmCloud/wasmCloud/commit/5225b1961038b815fe98c5250278d1aa483bdded)) - Enable `ring` feature for `async-nats` ([`81ab591`](https://github.com/wasmCloud/wasmCloud/commit/81ab5914e7d08740eb9371c9b718f13f0419c23f)) - Address clippy warnings ([`bd50166`](https://github.com/wasmCloud/wasmCloud/commit/bd50166619b8810ccdc2bcd80c33ff80d94bc909)) - Update to stream-based serving ([`0f70936`](https://github.com/wasmCloud/wasmCloud/commit/0f7093660a1ef09ff745daf5e1a96fd72c88984d)) - Conflate `wasi:blobstore/container` interface with `blobstore` ([`659cb2e`](https://github.com/wasmCloud/wasmCloud/commit/659cb2eace33962e3ed05d69402607233b33a951)) - Pass original component instance through the context ([`0707512`](https://github.com/wasmCloud/wasmCloud/commit/070751231e5bb4891b995e992e5206b3050ecc30)) - Upgrade `wrpc`, `async-nats`, `wasmtime` ([`9cb1b78`](https://github.com/wasmCloud/wasmCloud/commit/9cb1b784fe7a8892d73bdb40d1172b1879fcd932)) - Support ScaleComponentCommand w/ update ([`ed4b846`](https://github.com/wasmCloud/wasmCloud/commit/ed4b84661c08e43eadfce426474a49ad813ea6ec)) - Improve error messages for missing links ([`e7c3040`](https://github.com/wasmCloud/wasmCloud/commit/e7c30405302fcccc612209335179f0bc47d8e996)) - Improve error messages for missing links ([`20a7259`](https://github.com/wasmCloud/wasmCloud/commit/20a72597d17db8fcf0c70a7e9172edadcaad5b22)) - Allow empty payloads to trigger stop_host ([`e17fe93`](https://github.com/wasmCloud/wasmCloud/commit/e17fe933ffdc9b4e6938c4a0f2943c4813b658b1)) - Add link name to wRPC invocations ([`a0a1b8c`](https://github.com/wasmCloud/wasmCloud/commit/a0a1b8c0c3d82feb19f42c4faa6de96b99bac13f)) - Downgrade link/claims log/trace ([`d9a8c62`](https://github.com/wasmCloud/wasmCloud/commit/d9a8c62d6fce6e71edadcf7de78cac749cf58126)) - Setup debug traces ([`b014263`](https://github.com/wasmCloud/wasmCloud/commit/b014263cf3614995f597336bb40e51ab72bfa1c9)) - Propagate traces through components ([`fa1fde1`](https://github.com/wasmCloud/wasmCloud/commit/fa1fde185b47b055e511f6f2dee095e269db1651)) - Add support for configuring grpc protocol with opentelemetry ([`378b7c8`](https://github.com/wasmCloud/wasmCloud/commit/378b7c89c8b00a5dcee76c06bc8de615dc58f8aa)) - Replace actor references by component in crates ([`20c72ce`](https://github.com/wasmCloud/wasmCloud/commit/20c72ce0ed423561ae6dbd5a91959bec24ff7cf3)) - Updates host to support new wasm artifact type ([`0aa01a9`](https://github.com/wasmCloud/wasmCloud/commit/0aa01a92925dc12203bf9f06e13d21b7812b77eb)) - Bump oci-distribution to 0.11.0 ([`88c07bf`](https://github.com/wasmCloud/wasmCloud/commit/88c07bf3be18da4f4afac3e7e356ddc507a6d85e)) - Gracefully shutdown epoch interrupt thread ([`077a28a`](https://github.com/wasmCloud/wasmCloud/commit/077a28a6567a436c99368c7eb1bd5dd2a6bc6103)) - Generate changelogs after 1.0.1 release ([`4e0313a`](https://github.com/wasmCloud/wasmCloud/commit/4e0313ae4cfb5cbb2d3fa0320c662466a7082c0e)) - Updated with newest features ([`0f03f1f`](https://github.com/wasmCloud/wasmCloud/commit/0f03f1f91210a4ed3fa64a4b07aebe8e56627ea6)) - Generate crate changelogs ([`f986e39`](https://github.com/wasmCloud/wasmCloud/commit/f986e39450676dc598b92f13cb6e52b9c3200c0b)) - Count epoch in a separate OS thread ([`3eb4534`](https://github.com/wasmCloud/wasmCloud/commit/3eb453405aa144599f43bbaf56197566c9f0cf0a)) - Document invocation handling failures ([`c4b82f2`](https://github.com/wasmCloud/wasmCloud/commit/c4b82f28947f06253aa997ae65ab11ebcc507f49)) - Handle invocation handling errors ([`3cabf10`](https://github.com/wasmCloud/wasmCloud/commit/3cabf109f5b986079cceb7f125f75bf53348712e)) - Handle invocations in tasks ([`b8c3434`](https://github.com/wasmCloud/wasmCloud/commit/b8c34346137edf5492fe70abeb22336a33e85bc0)) - Remove redundant handler clone ([`1610702`](https://github.com/wasmCloud/wasmCloud/commit/1610702ad0f8cd3ba221c1b6b8ba2ce8fe57c6ae)) - Propagate `max_execution_time` to the runtime ([`a66921e`](https://github.com/wasmCloud/wasmCloud/commit/a66921edd9be3202d1296a165c34faf597b1dec1)) - Comment ([`ec3bae5`](https://github.com/wasmCloud/wasmCloud/commit/ec3bae5c03c77a0b77884b84754e33e1a8361a89)) - Check component update ref and respond with a message before task ([`45a3d3f`](https://github.com/wasmCloud/wasmCloud/commit/45a3d3f477b48e8a79e77880950bb785175a990d)) - Check component image reference on component update ([`95081ca`](https://github.com/wasmCloud/wasmCloud/commit/95081cacfc3fc04911c91c32f462d643be2e12ed)) - Limit max execution time to 10 minutes ([`e928020`](https://github.com/wasmCloud/wasmCloud/commit/e928020fd774abcc213fec560d89f128464da319)) - Replace references to 'actor' with 'component' ([`e6dd0b2`](https://github.com/wasmCloud/wasmCloud/commit/e6dd0b2809510e785f4ee4c531f5666e6ab21998)) - Update to Wasmtime 20 ([`33b50c2`](https://github.com/wasmCloud/wasmCloud/commit/33b50c2d258ca9744ed65b153a6580f893172e0c)) - Remove unnecessary todo comments ([`bdb519f`](https://github.com/wasmCloud/wasmCloud/commit/bdb519f91125c3f32f60ad9e9d1ce7bc1f147dc4)) - Expect stop_actor function parameter host_id to be unused ([`173bfa6`](https://github.com/wasmCloud/wasmCloud/commit/173bfa623328bd1790642ddd6d56c6f9e5b38831)) - Remove publish_event from stop_actor ([`c87f3fe`](https://github.com/wasmCloud/wasmCloud/commit/c87f3fe2654d5c874708974915bdd65f69f4afe1)) - Show provider ID on healthcheck failure messages ([`9f1b278`](https://github.com/wasmCloud/wasmCloud/commit/9f1b2787255cb106d98481019d26e3208c11fc9f)) - Improve error message for forceful provider shutdown ([`863296d`](https://github.com/wasmCloud/wasmCloud/commit/863296d7db28ca4815820f8b9a96a63dfe626904)) - Update URLs to `wrpc` org ([`e1ab91d`](https://github.com/wasmCloud/wasmCloud/commit/e1ab91d678d8191f28e2496a68e52c7b93ad90c3)) - Address clippy warnings ([`5957fce`](https://github.com/wasmCloud/wasmCloud/commit/5957fce86a928c7398370547d0f43c9498185441)) - Differentiate no config and config error ([`9542e16`](https://github.com/wasmCloud/wasmCloud/commit/9542e16b80c71dc7cc2f9e7175ebb25be050a242)) - Allow overwriting provider reference ([`dcbbc84`](https://github.com/wasmCloud/wasmCloud/commit/dcbbc843c5a571e1c33775c66bbd3cd528b02c26)) - Bumps host version to rc.2 ([`346753a`](https://github.com/wasmCloud/wasmCloud/commit/346753ab823f911b12de763225dfd154272f1d3a)) - Update `wrpc:keyvalue` in providers ([`9cd2b40`](https://github.com/wasmCloud/wasmCloud/commit/9cd2b4034f8d5688ce250429dc14120eaf61b483)) - Update `wasi:keyvalue` ([`a175419`](https://github.com/wasmCloud/wasmCloud/commit/a1754195fca5a13c8cdde713dad3e1a9765adaf5)) - Remove cluster_seed/cluster_issuers ([`bc5d296`](https://github.com/wasmCloud/wasmCloud/commit/bc5d296f3a58bc5e8df0da7e0bf2624d03335d9f)) - Imrpove wording for spec/provider ref mismatch ([`e8aac21`](https://github.com/wasmCloud/wasmCloud/commit/e8aac21cbc094f87fb486a903eaab9a132a7ee07)) - Warn scaling with different imageref ([`804d676`](https://github.com/wasmCloud/wasmCloud/commit/804d67665fac39c08a536b0902a65a85035e685e)) - Switch to `wit-bindgen-wrpc` ([`322f471`](https://github.com/wasmCloud/wasmCloud/commit/322f471f9a8154224a50ec33517c9f5b1716d2d5)) - Update `messaging` to `0.2.0` ([`955a689`](https://github.com/wasmCloud/wasmCloud/commit/955a6893792e86292883e76de57434616c28d380)) - Rename scaled ID from actor to component ([`91c57b2`](https://github.com/wasmCloud/wasmCloud/commit/91c57b238c6e3aec5bd86f5c2103aaec21932725)) - Don't clone targets with handlers ([`ef50f04`](https://github.com/wasmCloud/wasmCloud/commit/ef50f046ade176cabbf690de59caad5d4f99c78f)) - Rename ctl actor to component ([`bcbb402`](https://github.com/wasmCloud/wasmCloud/commit/bcbb402c2efe3dc881b06e666c70e01e94d3ad72)) - Removes old guest config and uses runtime config instead ([`6b2e1b5`](https://github.com/wasmCloud/wasmCloud/commit/6b2e1b5915a0e894a567622ffc193230e5654c1f)) - Rename actor_scale* events ([`9e23be2`](https://github.com/wasmCloud/wasmCloud/commit/9e23be23131bbcdad746f7e85d33d5812e5f2ff9)) - Deliver target links to started provider ([`2b500d7`](https://github.com/wasmCloud/wasmCloud/commit/2b500d7a38cb338620f9c7834ca7fef882e42c92)) - Actor -> Component ([`ef1d3af`](https://github.com/wasmCloud/wasmCloud/commit/ef1d3af1ccddf33cdb37763101e3fb7577bf1433)) - Remove capabilities ([`f34aac4`](https://github.com/wasmCloud/wasmCloud/commit/f34aac419d124aba6b6e252f85627847f67d01f4)) - Adds version to control API ([`3f2d2f4`](https://github.com/wasmCloud/wasmCloud/commit/3f2d2f44470d44809fb83de2fa34b29ad1e6cb30)) - Add label_changed event for label update/delete ([`dd0d449`](https://github.com/wasmCloud/wasmCloud/commit/dd0d449e5bfc3826675f3f744db44b3000c67197)) - Use native TLS roots along webpki ([`07b5e70`](https://github.com/wasmCloud/wasmCloud/commit/07b5e70a7f1321d184962d7197a8d98d1ecaaf71)) - Fix `link_name` functionality, reorganize tests ([`4ed3891`](https://github.com/wasmCloud/wasmCloud/commit/4ed38913f19fcd4dd44dfdcc9007e80e80cdc960)) - Convert to `wrpc:blobstore` ([`91874e9`](https://github.com/wasmCloud/wasmCloud/commit/91874e9f4bf2b37b895a4654250203144e12815c)) - Correct name and data streaming, update WIT ([`ccb3c73`](https://github.com/wasmCloud/wasmCloud/commit/ccb3c73dc1351b11233896abc068a200374df079)) - Use `wasmcloud:messaging` in providers ([`716d251`](https://github.com/wasmCloud/wasmCloud/commit/716d251478cf174085f6ff274854ddebd9e0d772)) - Recreates polyfill imports on update ([`5b4f75b`](https://github.com/wasmCloud/wasmCloud/commit/5b4f75b7b843483566983c72c3a25e91c3de3adc)) - Fetch configuration direct from bucket ([`5c3dc96`](https://github.com/wasmCloud/wasmCloud/commit/5c3dc963783c71fc91ec916be64a6f67917d9740)) - Fix deadlock and slow ack of update ([`fd85e25`](https://github.com/wasmCloud/wasmCloud/commit/fd85e254ee56abb65bee648ba0ea93b9a227a96f)) - Flatten claims response payload ([`cab6fd2`](https://github.com/wasmCloud/wasmCloud/commit/cab6fd2cae47f0a866f17dfdb593a48a9210bab8)) - Implement `wrpc:blobstore/blobstore` for FS ([`383b3f3`](https://github.com/wasmCloud/wasmCloud/commit/383b3f3067dddc913d5a0c052f7bbb9c47fe8663)) - Implement Redis `wrpc:keyvalue/{atomic,eventual}` ([`614af7e`](https://github.com/wasmCloud/wasmCloud/commit/614af7e3ed734c56b27cd1d2aacb0789a85e8b81)) - Implement `wasi:http/outgoing-handler` provider ([`e0dac9d`](https://github.com/wasmCloud/wasmCloud/commit/e0dac9de4d3a74424e3138971753db9da143db5a)) - Remove compat crate ([`f2aed15`](https://github.com/wasmCloud/wasmCloud/commit/f2aed15288300989aca03f899b095d3a71f8e5cd)) - Update `wrpc-interface-http` ([`c7a7ed7`](https://github.com/wasmCloud/wasmCloud/commit/c7a7ed73f5497f83a9dcfb509df580cdec3a4635)) - Address clippy warnings ([`adb08b7`](https://github.com/wasmCloud/wasmCloud/commit/adb08b70ecc37ec14bb9b7eea41c8110696d9b98)) - Race condition with initial config get ([`9fe1fe8`](https://github.com/wasmCloud/wasmCloud/commit/9fe1fe8ce8d4434fb05635d7d1ae6ee07bc188c3)) - Deliver full config with link ([`e14d040`](https://github.com/wasmCloud/wasmCloud/commit/e14d0405e9f746041001e101fc24320c9e6b4f9c)) - Update wRPC ([`95cfb6d`](https://github.com/wasmCloud/wasmCloud/commit/95cfb6d99f0e54243b2fb2618de39210d8f3694f)) - Start providers with named config ([`5c1a0a5`](https://github.com/wasmCloud/wasmCloud/commit/5c1a0a57e761d405cdbb8ea4cbca0fe13b7e8737)) - Refactor componentspec, deliver links to providers ([`188f096`](https://github.com/wasmCloud/wasmCloud/commit/188f0965e911067b5ffe9c62083fd4fbba2713f4)) - Use `&str` directly ([`6b369d4`](https://github.com/wasmCloud/wasmCloud/commit/6b369d49cd37a87dca1f92f31c4d4d3e33dec501)) - Use traces instead of tracing user-facing language to align with OTEL signal names ([`d65512b`](https://github.com/wasmCloud/wasmCloud/commit/d65512b5e86eb4d13e64cffa220a5a842c7bb72b)) - Add flags for overriding the default OpenTelemetry endpoint ([`6fe14b8`](https://github.com/wasmCloud/wasmCloud/commit/6fe14b89d4c26e5c01e54773268c6d0f04236e71)) - Switch to using --enable-observability and --enable- flags ([`868570b`](https://github.com/wasmCloud/wasmCloud/commit/868570be8d94a6d73608c7cde5d2422e15f9eb0c)) - Refactor component invocation tracking ([`95a9d7d`](https://github.com/wasmCloud/wasmCloud/commit/95a9d7d3b8c6367df93b65a2e218315cc3ec42eb)) - Improve target lookup error handling ([`149f98b`](https://github.com/wasmCloud/wasmCloud/commit/149f98b60c1e70d0e68153add3e30b8fb4483e11)) - Update wrpc_client ([`ec84fad`](https://github.com/wasmCloud/wasmCloud/commit/ec84fadfd819f203fe2e4906f5338f48f6ddec78)) - Move wasmcloud wrpc transport client to core ([`c654448`](https://github.com/wasmCloud/wasmCloud/commit/c654448653db224c6a676ecf43150d880a9daf8c)) - Re-tag request type enum policy ([`152186f`](https://github.com/wasmCloud/wasmCloud/commit/152186f9940f6c9352ee5d9f91ddefe5673bdac1)) - Support pubsub on wRPC subjects ([`76c1ed7`](https://github.com/wasmCloud/wasmCloud/commit/76c1ed7b5c49152aabd83d27f0b8955d7f874864)) - Include actor_id on scaled events ([`abb81eb`](https://github.com/wasmCloud/wasmCloud/commit/abb81ebbf99ec3007b1d1d48a43cfe52d86bf3e7)) - Cache request by unique data ([`df01397`](https://github.com/wasmCloud/wasmCloud/commit/df01397bce61344d3429aff081a9f9b23fad0b84)) - Formalize policy service ([`1fb6266`](https://github.com/wasmCloud/wasmCloud/commit/1fb6266826f47221ec3f9413f54a4c395622dcbd)) - Downgrade provider claims to optional metadata ([`be1e03c`](https://github.com/wasmCloud/wasmCloud/commit/be1e03c5281c9cf4b02fe5349a8cf5d0d7cd0892)) - Downgrade actor claims to optional metadata ([`8afb61f`](https://github.com/wasmCloud/wasmCloud/commit/8afb61fb6592db6a24c53f248e4f445f9b2db580)) - Glues in named config to actors ([`82c249b`](https://github.com/wasmCloud/wasmCloud/commit/82c249b15dba4dbe4c14a6afd2b52c7d3dc99985)) - Update wRPC ([`a96b1f3`](https://github.com/wasmCloud/wasmCloud/commit/a96b1f370392063f403e9f25e0ef21c30fdcdfa9)) - Implement AcceptorWithHeaders ([`1dc15a1`](https://github.com/wasmCloud/wasmCloud/commit/1dc15a127ac9830f3ebd21e61a1cf3db404eed6d)) - Instrument handle_invocation and call ([`a6ec7c3`](https://github.com/wasmCloud/wasmCloud/commit/a6ec7c3476daf63dc6f53afb7eb512cfc3d2b9d8)) - Implement wasmcloud_transport wrappers ([`fd50dcf`](https://github.com/wasmCloud/wasmCloud/commit/fd50dcfa07b759b01e32d7f974105615c8c47db4)) - Fixes write lock issue on policy service ([`4aa31f7`](https://github.com/wasmCloud/wasmCloud/commit/4aa31f74bf84784af0207d2886f62d833dfe1b63)) - Implement `wrpc:http/incoming-handler` ([`f2223a3`](https://github.com/wasmCloud/wasmCloud/commit/f2223a3f5378c3cebfec96b5322df619fcecc556)) - Begin incoming wRPC invocation implementation ([`fedfd92`](https://github.com/wasmCloud/wasmCloud/commit/fedfd92dbba773af048fe19d956f4c3625cc17de)) - Remove functionality related to wasmbus invocations ([`6784710`](https://github.com/wasmCloud/wasmCloud/commit/67847106d968a515ff89427454b7b14dfb486a3d)) - Switch to `wrpc` for `wasmcloud:messaging` ([`0c0c004`](https://github.com/wasmCloud/wasmCloud/commit/0c0c004bafb60323018fc1c86cb13493f72d29cd)) - Switch to `wrpc:{keyvalue,blobstore}` ([`5ede01b`](https://github.com/wasmCloud/wasmCloud/commit/5ede01b1fe0bc62234d2b7d6c72775d9e248a130)) - Encode custom parameters as tuples ([`f3bc961`](https://github.com/wasmCloud/wasmCloud/commit/f3bc96128ed7033d08bc7da1ea7ba89c40880ede)) - Implement `wrpc:http/outgoing-handler.handle` ([`2463845`](https://github.com/wasmCloud/wasmCloud/commit/246384524cfe65ce6742558425b885247b461c5c)) - Correctly invoke custom functions ([`9e304cd`](https://github.com/wasmCloud/wasmCloud/commit/9e304cd7d19a2f7eef099703f168e8f155d4f8bc)) - Update wRPC ([`49d8650`](https://github.com/wasmCloud/wasmCloud/commit/49d86501487f6811bb8b65641c40ab353f6e110d)) - Wrap all ctl operations in CtlResponse ([`4a4b300`](https://github.com/wasmCloud/wasmCloud/commit/4a4b300515e9984a1befe6aaab1a6298d8ea49b1)) - Consistent host operations ([`2798858`](https://github.com/wasmCloud/wasmCloud/commit/2798858880004225ebe49aa1d873019a02f29e49)) - Revert incorrectly handled config conficts ([`e12ec1d`](https://github.com/wasmCloud/wasmCloud/commit/e12ec1d6655a9aa319236a8d62a53fd6521bd683)) - Remove collection type aliases ([`e16da66`](https://github.com/wasmCloud/wasmCloud/commit/e16da6614ad9ae28e8c3e6ac3ebb36faf12cb4d1)) - Remove plural actor events ([`9957ca7`](https://github.com/wasmCloud/wasmCloud/commit/9957ca7f8b21444b2d4e32f20a50b09f92a5b6ee)) - Flatten instances on actor/providers ([`5275937`](https://github.com/wasmCloud/wasmCloud/commit/5275937c2c9b25139f3c208af7909889362df308)) - Fully support interface links, remove aliases ([`48fc893`](https://github.com/wasmCloud/wasmCloud/commit/48fc893ba2de576511aeea98a3da4cc97024c53e)) - Bindgen issues preventing builds ([`e9bea42`](https://github.com/wasmCloud/wasmCloud/commit/e9bea42ed6189d903ea7fc6b7d4dc54a6fe88a12)) - Integrate set-link-name and wrpc ([`4f55396`](https://github.com/wasmCloud/wasmCloud/commit/4f55396a0340d65dbebdf6d4f0ca070d6f990fc4)) - Support component invoking polyfilled functions ([`5173aa5`](https://github.com/wasmCloud/wasmCloud/commit/5173aa5e679ffe446f10aa549f1120f1bd1ab033)) - Remove unused imports/functions ([`5990b00`](https://github.com/wasmCloud/wasmCloud/commit/5990b00ea49b1bfeac3ee913dc0a9188729abeff)) - Support wrpc component exports ([`49e5943`](https://github.com/wasmCloud/wasmCloud/commit/49e5943d9a087b5ef5428f73281c36030d77502c)) - Change set-target to set-link-name ([`5d19ba1`](https://github.com/wasmCloud/wasmCloud/commit/5d19ba16a98dca9439628e8449309ccaa763ab10)) - Remove module support ([`fec6f5f`](https://github.com/wasmCloud/wasmCloud/commit/fec6f5f1372a1de5737f5ec585ad735e14c20480)) - Remove unused function ([`1bda5cd`](https://github.com/wasmCloud/wasmCloud/commit/1bda5cd0da34dcf2d2613fca13430fac2484b5d9)) - Reintroduce wasmbus over wrpc ([`a90b0ea`](https://github.com/wasmCloud/wasmCloud/commit/a90b0eaccdeb095ef147bed58e262440fb5f8486)) - Support interface link put, component spec ([`5af1138`](https://github.com/wasmCloud/wasmCloud/commit/5af1138da6afa3ca6424d4ff10aa49211952c898)) - Add invocation and error counts for actor invocations ([`7d51408`](https://github.com/wasmCloud/wasmCloud/commit/7d51408440509c687b01e00b77a3672a8e8c30c9)) - Changes config topic to be for named config ([`1d46c28`](https://github.com/wasmCloud/wasmCloud/commit/1d46c284e32d2623d0b105014ef0c2f6ebc7e079)) - Updates topics to the new standard ([`42d069e`](https://github.com/wasmCloud/wasmCloud/commit/42d069eee87d1b5befff1a95b49973064f1a1d1b)) - Add initial support for metrics ([`17648fe`](https://github.com/wasmCloud/wasmCloud/commit/17648fedc2a1907b2f0c6d053b9747e72999addb)) - Set log_level for providers ([`637810b`](https://github.com/wasmCloud/wasmCloud/commit/637810b996b59bb4d576b6c1321e0363b1396fe5)) - Fix clippy warning, added ; for consistency, return directly the instance instead of wrapping the instance's components in a future ([`c6fa704`](https://github.com/wasmCloud/wasmCloud/commit/c6fa704f001a394c10f8769d670941aff62d6414)) - Add comments, remove useless future::ready ([`7db1183`](https://github.com/wasmCloud/wasmCloud/commit/7db1183dbe84aeeb1967eb28d71876f6f175c2c2)) - Fmt ([`1d3fd96`](https://github.com/wasmCloud/wasmCloud/commit/1d3fd96f2fe23c71b2ef70bb5199db8009c56154)) - Fix(1365): Encapsulate in spawn instance's process in response to a nats event. Also encapsulate the .clone on the wasmtime module. After this two modification the workload spread on all core of the CPU. Relates to issue https://github.com/wasmCloud/wasmCloud/issues/1365 ([`ba7590a`](https://github.com/wasmCloud/wasmCloud/commit/ba7590ab56083173f2abbe214add648e32c2591d)) - Fix `wasmcloud-host` clippy warning ([`50c8244`](https://github.com/wasmCloud/wasmCloud/commit/50c82440b34932ed5c03cb24a45fbacfe0c3e4d3)) - Update version to 0.82.0 ([`aa03d41`](https://github.com/wasmCloud/wasmCloud/commit/aa03d411b571e446a842fa0e6b506436e5a04e4c)) - Implement preview 2 interfaces ([`08b8a3c`](https://github.com/wasmCloud/wasmCloud/commit/08b8a3c72902e6d8ff4f9dcaa95b9649f3716e75)) - Update to wasmtime 17 ([`49f3883`](https://github.com/wasmCloud/wasmCloud/commit/49f3883c586c098d4b0be44793057b97566ec2e1)) - Move label parsing out of host library ([`fe7592b`](https://github.com/wasmCloud/wasmCloud/commit/fe7592b1a5501f3faa8bcf3bf45edf4032e92f0b)) - Add subject to control interface logs ([`38faeac`](https://github.com/wasmCloud/wasmCloud/commit/38faeace04d4a43ee87eafdfa129555370cddecb)) - Remove requirement for actors to have capabilities in claims ([`7b2d635`](https://github.com/wasmCloud/wasmCloud/commit/7b2d635949e2ebdb367eefb0b4ea69bf31590a7d)) - Add README for the host crate ([`7bf02ed`](https://github.com/wasmCloud/wasmCloud/commit/7bf02ede2e92aed19bbf7ef5162e2a87dc8f5cb8)) - Rename lattice prefix to just lattice ([`6e8faab`](https://github.com/wasmCloud/wasmCloud/commit/6e8faab6a6e9f9bb7327ffb71ded2a83718920f7)) - Publish claims with actor_scaled ([`39849b5`](https://github.com/wasmCloud/wasmCloud/commit/39849b5f2fde4d80ccfd48c3c765c258800645ea)) - Add heartbeat fields to inventory ([`2e8893a`](https://github.com/wasmCloud/wasmCloud/commit/2e8893af27700b86dbeb63e5e7fc4252ec6771e1)) - Change heartbeat payload to inventory ([`032e509`](https://github.com/wasmCloud/wasmCloud/commit/032e50925e2e64c865a82cbb90de7da1f99d995e)) - Remove singular actor events, add actor_scaled ([`df01bbd`](https://github.com/wasmCloud/wasmCloud/commit/df01bbd89fd2b690c2d1bcfe68455fb827646a10)) - Upgrade max_instances to u32 ([`5cca9ee`](https://github.com/wasmCloud/wasmCloud/commit/5cca9ee0a88d63cb53e8d352c16a5d9d59966bc8)) - Rename max-concurrent to max-instances, simplify scale ([`d8eb9f3`](https://github.com/wasmCloud/wasmCloud/commit/d8eb9f3ee9df65e96d076a6ba11d2600d0513207)) - Bump wasmcloud to 0.81 ([`c038aa7`](https://github.com/wasmCloud/wasmCloud/commit/c038aa74a257664780719103c7362a747fc5a539)) - Remove deprecated code related to start actor cmd ([`7de3182`](https://github.com/wasmCloud/wasmCloud/commit/7de31820034c4b70ab6edc772713e64aafe294a9)) - Override previous call alias on clash ([`9d1f67f`](https://github.com/wasmCloud/wasmCloud/commit/9d1f67f37082597c25ae8a7239321d8d2e752b4d)) - Update format for serialized claims ([`37618a3`](https://github.com/wasmCloud/wasmCloud/commit/37618a316baf573cc31311ad3ae78cd054e0e2b5)) - Add event name as suffix on event topic ([`6994a22`](https://github.com/wasmCloud/wasmCloud/commit/6994a2202f856da93d0fe50e40c8e72dd3b7d9e6)) - Rename label to key ([`bdb72ee`](https://github.com/wasmCloud/wasmCloud/commit/bdb72eed8778a5d8c59d0b8939f147c374cb671f)) - Use consistent message prefix ([`9a086ec`](https://github.com/wasmCloud/wasmCloud/commit/9a086ec818dcb0292d332f606f49e04c503866b4)) - Enable updating host labels via the control interface ([`85cb573`](https://github.com/wasmCloud/wasmCloud/commit/85cb573d29c75eae4fdaca14be808131383ca3cd)) - Adds some additional context around test failures I was seeing ([`64d21b1`](https://github.com/wasmCloud/wasmCloud/commit/64d21b1f3d413e4c5da78d8045c1366c3782a190)) - Adds support for actor config ([`1a048a7`](https://github.com/wasmCloud/wasmCloud/commit/1a048a71320dbbf58f331e7e958f4b1cd5ed4537)) - Address clippy issue ([`9f9ca40`](https://github.com/wasmCloud/wasmCloud/commit/9f9ca40e7a4b1d2d553fabee8a8bfc3f49e85a3f)) - Remove support for prov_rpc NATS connection ([`545c21c`](https://github.com/wasmCloud/wasmCloud/commit/545c21cedd1475def0648e3e700bcdd15f800c2a)) - Remove `local` host ([`c8240e2`](https://github.com/wasmCloud/wasmCloud/commit/c8240e200c5fab84cfc558efc6445ecc91a9fa24)) - Remove support for bindle references ([`5301084`](https://github.com/wasmCloud/wasmCloud/commit/5301084bde0db0c65811aa30c48de2a63e091fcf)) - Polish tracing and logging levels ([`2389f27`](https://github.com/wasmCloud/wasmCloud/commit/2389f27f0b570164a895a37abd462be2d68f20be)) - Implement wasifills for simple types ([`cfb66f8`](https://github.com/wasmCloud/wasmCloud/commit/cfb66f81180a3b47d6e7df1a444a1ec945115b15)) - Disambiguate traced function names ([`2c77841`](https://github.com/wasmCloud/wasmCloud/commit/2c778413dd347ade2ade472365545fc954da20d0)) - Disable handle_links trace until wadm sends fewer requests ([`7e53ed5`](https://github.com/wasmCloud/wasmCloud/commit/7e53ed56244bf4c3232b390dd1c3984dbc00be74)) - Queue subscribe to linkdefs and get topics ([`1a86faa`](https://github.com/wasmCloud/wasmCloud/commit/1a86faa9af31af3836da95c4c312ebedaa90c6bc)) - Update ctl to 0.31.0 ([`a1e8d3f`](https://github.com/wasmCloud/wasmCloud/commit/a1e8d3f09e039723d28d738d98b47bce54e4450d)) - 'upstream/main' into `merge/wash` ([`0f967b0`](https://github.com/wasmCloud/wasmCloud/commit/0f967b065f30a0b5418f7ed519fdef3dc75a6205)) - Drop write locks immediately ([`a8e1c0d`](https://github.com/wasmCloud/wasmCloud/commit/a8e1c0d6f9aa461bf8e26b68092135f90f523573)) - Drop problematic write lock ([`774bb04`](https://github.com/wasmCloud/wasmCloud/commit/774bb0401d141c59cdd8c73e716f5d8c00002ea0)) - Implement outgoing HTTP ([`2e8982c`](https://github.com/wasmCloud/wasmCloud/commit/2e8982c962f1cbb15a7a0e34c5a7756e02bb56a3)) - Publish correct number of actor events ([`8fdddcc`](https://github.com/wasmCloud/wasmCloud/commit/8fdddccf5931cd10266a13f02681fdbfb34aba37)) - Stop sending linkdef events on startup ([`e9a3917`](https://github.com/wasmCloud/wasmCloud/commit/e9a391726ad1b7a2e01bab5be09cd090f35fe661)) - Bump crate versions ([`d163240`](https://github.com/wasmCloud/wasmCloud/commit/d16324054a454347044f7cc052da1bbd4324a284)) - Improve reference parsing ([`d377cb4`](https://github.com/wasmCloud/wasmCloud/commit/d377cb4553519413e420f9a547fef7ecf2421591)) - Add logs related to registry config ([`75c200d`](https://github.com/wasmCloud/wasmCloud/commit/75c200da45e383d02b2557df0bc9db5edb5f9979)) - Add some control interface logs ([`02ae070`](https://github.com/wasmCloud/wasmCloud/commit/02ae07006c9b2bb7b58b79b9e581ba255027fc7d)) - Change expected host label prefix to remove collision with WASMCLOUD_HOST_SEED ([`3fb60ee`](https://github.com/wasmCloud/wasmCloud/commit/3fb60eeca9e122f245b60885bdf13082c3697f04)) - Resolve 1.73.0 warnings ([`93c0981`](https://github.com/wasmCloud/wasmCloud/commit/93c0981a4d69bc8f8fe06e6139e78e7f700a3115)) - Fixes #746 ([`ac935a8`](https://github.com/wasmCloud/wasmCloud/commit/ac935a8028d2ba6a3a356c6e28c3681492bc09a1)) - Give NATS 2 secs to start in test ([`a4b284c`](https://github.com/wasmCloud/wasmCloud/commit/a4b284c182278542b25056f32c86480c490a67b4)) - Use max concurrency instead of count ([`97ecbb3`](https://github.com/wasmCloud/wasmCloud/commit/97ecbb34f81f26a36d26f458c8487e05dafa101e)) - Return an InvocationResponse when failing to decode an invocation ([`214c5c4`](https://github.com/wasmCloud/wasmCloud/commit/214c5c4cce254b641d93882795b6f48d61dcc4f9)) - Remove unnecessary mut ([`f4611f3`](https://github.com/wasmCloud/wasmCloud/commit/f4611f31e12227ed1257bb95809f9542d1de6353)) - Deprecate HOST_ label prefix in favor of WASMCLOUD_HOST_ ([`88b2f2f`](https://github.com/wasmCloud/wasmCloud/commit/88b2f2f5b2424413f80d71f855185304fb003de5)) - Rename SUCCESS to ACCEPTED, None concurrent max ([`cd8f69e`](https://github.com/wasmCloud/wasmCloud/commit/cd8f69e8d155f3e2aa5169344ff827e1f7d965cf)) - Handle ctl requests concurrently ([`44019a8`](https://github.com/wasmCloud/wasmCloud/commit/44019a895bdb9780abea73a4dc740febf44dff6f)) - Download actor to scale in task ([`ebe70f3`](https://github.com/wasmCloud/wasmCloud/commit/ebe70f3e8a2ae095a56a16b954d4ac20f4806364)) - Parse labels from args ([`977feaa`](https://github.com/wasmCloud/wasmCloud/commit/977feaa1bca1ae4df625c8061f2f5330029739b4)) - Drop logging level to trace ([`8ffa131`](https://github.com/wasmCloud/wasmCloud/commit/8ffa1317b1f106d6dcd2ec01c41fa14e6e41966e)) - Proxy RUST_LOG to providers ([`691c371`](https://github.com/wasmCloud/wasmCloud/commit/691c3719b8030e437f565156ad5b9cff12fd4cf3)) - Reduce verbosity of instrumented functions ([`0023f7e`](https://github.com/wasmCloud/wasmCloud/commit/0023f7e86d5a40a534f623b7220743f27871549e)) - Rework host shutdown ([`2314f5f`](https://github.com/wasmCloud/wasmCloud/commit/2314f5f4d49c5b98949fe5d4a1eb692f1fad92b7)) - Bump to `0.79.0` ([`578c72d`](https://github.com/wasmCloud/wasmCloud/commit/578c72d3333f1b9c343437946114c3cd6a0eead4)) - Update dependencies ([`22276ff`](https://github.com/wasmCloud/wasmCloud/commit/22276ff61bcb4992b557f7af6624c9715f72c32b)) - Remove instance pooling ([`017e6d4`](https://github.com/wasmCloud/wasmCloud/commit/017e6d40841f14b2158cf2ff70ca2ac8940e4b84)) - Enforce unique image references for actors ([`3cef088`](https://github.com/wasmCloud/wasmCloud/commit/3cef088e82a9c35b2cef76ba34440213361563e4)) - Properly format actors_started claims ([`28d2d6f`](https://github.com/wasmCloud/wasmCloud/commit/28d2d6fc5e68ab8de12771fb3b0fb00617b32b30)) - Satisfy clippy linting ([`1a80eea`](https://github.com/wasmCloud/wasmCloud/commit/1a80eeaa1f1ba333891092f8a27e924511c0bd68)) - Support annotation filters for stop/scale ([`ba675c8`](https://github.com/wasmCloud/wasmCloud/commit/ba675c868d6c76f4e717f64d0d6e93affea9398d)) - Flushes clients when responding to ctl requests ([`bdd0964`](https://github.com/wasmCloud/wasmCloud/commit/bdd0964cf6262c262ee167993f5d6d48994c941d)) - Proxy SYSTEMROOT to providers on Windows ([`f4ef770`](https://github.com/wasmCloud/wasmCloud/commit/f4ef770dda0af0c1e7df607abbe45888d819260a)) - Publish periodic provider health status ([`68c4158`](https://github.com/wasmCloud/wasmCloud/commit/68c41586cbff172897c9ef3ed6358a66cd9cbb94)) - Use named fields when publishing link definitions to providers ([`b2d2415`](https://github.com/wasmCloud/wasmCloud/commit/b2d2415a0370ff8cae65b530953f33a07bb7393a)) - Allow namespaces with slashes ([`1829b27`](https://github.com/wasmCloud/wasmCloud/commit/1829b27213e836cb347a542e9cdc771c74427892)) - Look for invocation responses from providers ([`7502bcb`](https://github.com/wasmCloud/wasmCloud/commit/7502bcb569420e2d402bf66d8a5eff2e6481a80b)) - Store claims on fetch ([`43a75f3`](https://github.com/wasmCloud/wasmCloud/commit/43a75f3b222d99259c773f990ef8ae4754d3b6fc)) - Implement `ResourceRef::authority` ([`ec2d0c1`](https://github.com/wasmCloud/wasmCloud/commit/ec2d0c134cd02dcaf3981d94826935c17b512d4e)) - Introduce artifact fetchers ([`0261297`](https://github.com/wasmCloud/wasmCloud/commit/0261297230f1be083af15e257c967635654c2b71)) - Derive `Default` for `Auth` ([`21a7e3f`](https://github.com/wasmCloud/wasmCloud/commit/21a7e3f4728a8163a6916b5d1817bac238b6fd46)) - Rename `RegistrySettings` -> `RegistryConfig` ([`7799e38`](https://github.com/wasmCloud/wasmCloud/commit/7799e38ecc91c13add5213b72f5e56a5b9e01c6e)) - Rework fetching logic ([`0a86d89`](https://github.com/wasmCloud/wasmCloud/commit/0a86d89a7b57329145e032b3dc2ac999d5f0f812)) - Be explicit about `async_nats` imports ([`9f9d0e4`](https://github.com/wasmCloud/wasmCloud/commit/9f9d0e4da2fafb368fa11fd5e692ded6d912d6e5)) - Clean-up imports ([`4e4d585`](https://github.com/wasmCloud/wasmCloud/commit/4e4d5856ae622650d1b74f2c595213ef12559d9d)) - Expose registry as a public module ([`d104226`](https://github.com/wasmCloud/wasmCloud/commit/d1042261b6b96658af4032f5f10e5144b9a14717)) - Emit more clear start message ([`5923e34`](https://github.com/wasmCloud/wasmCloud/commit/5923e34245c498bd9e7206bbe4ac6690192c7c60)) - Attach traces on inbound and outbound messages ([`74142c4`](https://github.com/wasmCloud/wasmCloud/commit/74142c4cff683565fb321b7b65fbb158b5a9c990)) - Flushes NATS clients on host stop ([`99aa2fe`](https://github.com/wasmCloud/wasmCloud/commit/99aa2fe060f1e1fe7820d7f0cc41cc2584c1e533)) - Reduce verbosity on actor logs ([`6c42d5c`](https://github.com/wasmCloud/wasmCloud/commit/6c42d5c50375cdc2d12c86513a98b45135f0d187)) - Implement `wasi:logging` for actors ([`05f452a`](https://github.com/wasmCloud/wasmCloud/commit/05f452a6ec1644db0fd9416f755fe0cad9cce6d3)) - Ignore `stop_provider` annotations ([`9e61a11`](https://github.com/wasmCloud/wasmCloud/commit/9e61a113c750e885316144681946187e5c113b49)) - Bump version to `0.78.0` ([`801377a`](https://github.com/wasmCloud/wasmCloud/commit/801377a4445cfb4c1c61a8b8f9ecbe956996272b)) - Flatten optional annotations to always be set ([`463a2fb`](https://github.com/wasmCloud/wasmCloud/commit/463a2fbc7887ac7f78d32ccd19266630f5914f2e)) - Address nits ([`019f63b`](https://github.com/wasmCloud/wasmCloud/commit/019f63bd9b46f68fc4703242c17cc3e38f0f889c)) - Unwrap expired ([`59e98a9`](https://github.com/wasmCloud/wasmCloud/commit/59e98a997a4b6cc371e4983c42fb6609b73f7b53)) - Handle stored claims without config_schema ([`680def6`](https://github.com/wasmCloud/wasmCloud/commit/680def637270c23541d9263db47e9834a9081809)) - Reduce noise from REFMAP entries ([`9091898`](https://github.com/wasmCloud/wasmCloud/commit/90918988a075ea7c0a110cf5301ce917f5822c3b)) - Reduce noise on instruments ([`11c932b`](https://github.com/wasmCloud/wasmCloud/commit/11c932b6838aa987eb0122bc50067cee3417025b)) - Return invocation responses for host failures ([`c63b650`](https://github.com/wasmCloud/wasmCloud/commit/c63b6500264128904e9021cea2e3490a74d04107)) - Support policy service ([`2ebdab7`](https://github.com/wasmCloud/wasmCloud/commit/2ebdab7551f6da93967d921316cae5d04a409a43)) - Pub the context mod only with the otel feature enabled ([`45b0fb0`](https://github.com/wasmCloud/wasmCloud/commit/45b0fb0960921a4eebd335977fd8bc747def97a4)) - Use cached links for queries ([`f2bf50d`](https://github.com/wasmCloud/wasmCloud/commit/f2bf50dc6c2cda49c4d82a877aaf554f153f494a)) - Add support for call aliases ([`123cb2f`](https://github.com/wasmCloud/wasmCloud/commit/123cb2f9b8981c37bc333fece71c009ce875e30f)) - Make content_length a required field ([`6428747`](https://github.com/wasmCloud/wasmCloud/commit/642874717b6aab760d4692f9e8b12803548314e2)) - Use skip_all ([`782a53e`](https://github.com/wasmCloud/wasmCloud/commit/782a53ebb8a682197ebb47f4f7651dc075690e22)) - Replace needs_chunking function with direct comparison ([`6de67aa`](https://github.com/wasmCloud/wasmCloud/commit/6de67aa1ddab22ec99fe70f2c2fdc92dc5760b06)) - Move longer fields to their own lines ([`c47ee0c`](https://github.com/wasmCloud/wasmCloud/commit/c47ee0cdd3225c25d2ef54bee1bbc42b39375b65)) - Remove noisy fields from instruments ([`4fb8206`](https://github.com/wasmCloud/wasmCloud/commit/4fb8206e1d5fb21892a01b9e4f009e48c8bea2df)) - Support chunking and dechunking of requests ([`813ce52`](https://github.com/wasmCloud/wasmCloud/commit/813ce52a9c11270814eec051dfaa8817bf9f567d)) - Implement `wasi:blobstore` ([`bef159a`](https://github.com/wasmCloud/wasmCloud/commit/bef159ab4d5ce6ba73e7c3465110c2990da64eac)) - Remove redundant claim clone ([`11ea950`](https://github.com/wasmCloud/wasmCloud/commit/11ea950ee26e4b7b7909d04c3505c80b4939efbb)) - Always include cluster key as a valid issuer ([`64592ed`](https://github.com/wasmCloud/wasmCloud/commit/64592ede426193873de52fde8cf98611b6a872a8)) - Update imports ([`a8538fb`](https://github.com/wasmCloud/wasmCloud/commit/a8538fb7926b190a180bdd2b46ad00757d98759a)) - Pass OTEL settings to providers via deprecated env vars ([`47f4548`](https://github.com/wasmCloud/wasmCloud/commit/47f45487b46891cfbab5611ee41f52c6582a1dd8)) - Construct a strongly typed HostData to send to providers ([`23f1759`](https://github.com/wasmCloud/wasmCloud/commit/23f1759e818117f007df8d9b1bdfdfa7710c98c5)) - Support OTEL traces end-to-end ([`675d364`](https://github.com/wasmCloud/wasmCloud/commit/675d364d2f53f9dbf7ebb6c655d5fbbbba6c62b6)) - Satisfy clippy ([`f2246c0`](https://github.com/wasmCloud/wasmCloud/commit/f2246c07cf38a6f142d7ce58e0623f8da5adbe83)) - Validate invocations for antiforgery and claims ([`ccec9ed`](https://github.com/wasmCloud/wasmCloud/commit/ccec9edac6c91def872ca6a1a56f62ea716e84a2)) - Send OTEL config via HostData ([`c334d84`](https://github.com/wasmCloud/wasmCloud/commit/c334d84d01b8b92ab9db105f8e6f0c4a6bcef8b1)) - Stop unnecessarily satisfying clippy ([`594254a`](https://github.com/wasmCloud/wasmCloud/commit/594254af85aeaccae50337d3a8514714d11d2720)) - Add support for putting registry credentials via control interface ([`002c993`](https://github.com/wasmCloud/wasmCloud/commit/002c9931e7fa309c39df26b313f16976e3a36001)) - Support registry settings via config service and command-line flags ([`48d4557`](https://github.com/wasmCloud/wasmCloud/commit/48d4557c8ee895278055261bccb1293806b308b0)) - Store claims when the scale triggers the startup actor ([`a44cd43`](https://github.com/wasmCloud/wasmCloud/commit/a44cd43b7baad0d9c332d3e7c3a52eb0f4e5b6c8)) - Partially implement `wasi:keyvalue/atomic` ([`d434e14`](https://github.com/wasmCloud/wasmCloud/commit/d434e148620d394856246ac34bb0a64c37181970)) - Implement provider health checks ([`72b7609`](https://github.com/wasmCloud/wasmCloud/commit/72b7609076ca3b97faf1c4a14489d1f466cf477a)) - Ignore empty responses ([`02bc0c4`](https://github.com/wasmCloud/wasmCloud/commit/02bc0c4f348da19f058787da9a314dd9b634c6ae)) - Store typed keys, not strings ([`75a1fb0`](https://github.com/wasmCloud/wasmCloud/commit/75a1fb075357ac2566fef1b45c930e6c400a4041)) - Establish NATS connections concurrently ([`0db5a5b`](https://github.com/wasmCloud/wasmCloud/commit/0db5a5ba5b20535e16af46fd92f7040c8174d636)) - Implement `wasmcloud:http/incoming-handler` support ([`50d0ed1`](https://github.com/wasmCloud/wasmCloud/commit/50d0ed1086c5f417ed64dcce139cc3c2b50ca14c)) - Rename friendly noun ([`b77767e`](https://github.com/wasmCloud/wasmCloud/commit/b77767e6d3c32ceba0b4e5b421b532ac0788dc15)) - Implement structured logging ([`ed64180`](https://github.com/wasmCloud/wasmCloud/commit/ed64180714873bd9be1f9008d29b09cbf276bba1)) - Respect allow_file_load ([`ff02491`](https://github.com/wasmCloud/wasmCloud/commit/ff024913d3107dc65dd8aad69a1f598390de6d1a)) - Revert "feat: delete claims when actors or providers are stopped" ([`1089ca1`](https://github.com/wasmCloud/wasmCloud/commit/1089ca1f5c35a9c75c2e397738a1c2a871f4cc2e)) - Delete claims when actors or providers are stopped ([`31b76fd`](https://github.com/wasmCloud/wasmCloud/commit/31b76fd2754e1962df36340275ad5179576c8d07)) - Properly handle empty responses ([`d9775af`](https://github.com/wasmCloud/wasmCloud/commit/d9775af7c953749f37978802c690ee29838f0da6)) - Use `wasmcloud-compat` structs ([`5ce8d6a`](https://github.com/wasmCloud/wasmCloud/commit/5ce8d6a241f36d76013de1cc5827bf690fc62911)) - Remove actor links on deletion ([`958aad5`](https://github.com/wasmCloud/wasmCloud/commit/958aad5ce94120322a920be71626c1aa6a349d0c)) - Implement link names and a2a calls ([`2e3bd2b`](https://github.com/wasmCloud/wasmCloud/commit/2e3bd2bd7611e5de9fe123f53778f282613eb0de)) - Do not proxy env vars from host to providers ([`33ef4f3`](https://github.com/wasmCloud/wasmCloud/commit/33ef4f34a5748e445f01148ec7d00bb0f01c1606)) - Fill in missing data in host pings and heartbeat messages ([`6fd0049`](https://github.com/wasmCloud/wasmCloud/commit/6fd00493232a2c860e94f6263a3a0876ad7a6acb)) - Refactor connection opts ([`5cd8afe`](https://github.com/wasmCloud/wasmCloud/commit/5cd8afe68e4c481dcf09c9bebb125a9e4667ed1e)) - Enforce rpc_timeout ([`39da3e7`](https://github.com/wasmCloud/wasmCloud/commit/39da3e77462d26c8d8d2a290ce33f29a954e83ba)) - Implement ctl_topic_prefix ([`3588b5f`](https://github.com/wasmCloud/wasmCloud/commit/3588b5f9ce2f0c0a4718d9bd576904ef77682304)) - Implement rpc,ctl,prov_rpc connections ([`921fa78`](https://github.com/wasmCloud/wasmCloud/commit/921fa784ba3853b6b0a622c6850bb6d71437a011)) - Remove constants ([`ce93e4a`](https://github.com/wasmCloud/wasmCloud/commit/ce93e4aad4148a51c2d30b58bdccd17ef38a9954)) - Remove unnecessary allocations ([`a9f3ba0`](https://github.com/wasmCloud/wasmCloud/commit/a9f3ba05665d0fe7b36f0df5ed4c202dafadd0bf)) - Add claims and link query functionality ([`d367812`](https://github.com/wasmCloud/wasmCloud/commit/d367812a666acced17f1c0f795c53ac8cf416cc6)) - Introduce `wasmcloud-compat` crate ([`2b07909`](https://github.com/wasmCloud/wasmCloud/commit/2b07909e484f13d64ad54b649a5b8e9c36b48227)) - Avoid fetching actor bytes twice when scaling actor ([`02d18b6`](https://github.com/wasmCloud/wasmCloud/commit/02d18b62d6777ca714e2de618d3fab914ce47ab1)) - Generate host name based on a random number ([`556da3f`](https://github.com/wasmCloud/wasmCloud/commit/556da3fb0666f61f140eefef509913f1d34384a3)) - Made fetch arg ordering consistent ([`478f775`](https://github.com/wasmCloud/wasmCloud/commit/478f775eb79bc955af691a7b5c7911cc36e8c98f)) - Use allow_latest and allowed_insecure config ([`7c389be`](https://github.com/wasmCloud/wasmCloud/commit/7c389bee17d34db732babde7724286656c268f65)) - Use js_domain provided by cli ([`9897b90`](https://github.com/wasmCloud/wasmCloud/commit/9897b90e845470faa35e8caf4816c29e6dcefd91)) - Implement graceful provider shutdown delay ([`7d290aa`](https://github.com/wasmCloud/wasmCloud/commit/7d290aa08b2196a6082972a4d662bf1a93d07dec)) - Maintain cluster issuers list ([`194f791`](https://github.com/wasmCloud/wasmCloud/commit/194f791c16ad6a7106393b4bcf0d0c51a70f638d)) - Matches up base64 encoding to what providers expected ([`7a84469`](https://github.com/wasmCloud/wasmCloud/commit/7a84469dae07cd31185dbb0ad6cfd0af02d0e3a3)) - Add support for non-default link names ([`a5db5e5`](https://github.com/wasmCloud/wasmCloud/commit/a5db5e5c0d13d66bf8fbf0da7c4f3c10021d0f90)) - Add support for custom lattice prefix ([`c9fecb9`](https://github.com/wasmCloud/wasmCloud/commit/c9fecb99793649a6f9321b9224f85b9472889dec)) - Implement `wasmcloud:messaging/consumer` support ([`77d663d`](https://github.com/wasmCloud/wasmCloud/commit/77d663d3e1fd5590177ac8003a313a3edf29ab1f)) - Implement `wasi:keyvalue/readwrite` support ([`02c1ddc`](https://github.com/wasmCloud/wasmCloud/commit/02c1ddc0d62b40f63afe4d270643ebc3bf39c081)) - Handle launch commands concurrently ([`cf3c76a`](https://github.com/wasmCloud/wasmCloud/commit/cf3c76a96c7fb411d0c286a687ccf1633cb5feeb)) - Rename most instances of lattice and wasmbus to host ([`f3f6c21`](https://github.com/wasmCloud/wasmCloud/commit/f3f6c21f25632940a6cc1d5290f8e84271609496)) - Use context ([`c17d742`](https://github.com/wasmCloud/wasmCloud/commit/c17d7426de06282d8f9d867ef227dc59d4227965)) - Create bucket explicitly instead of stream ([`6b3080a`](https://github.com/wasmCloud/wasmCloud/commit/6b3080a8f655ce36b0cc6ef381ae0bf40e0e2a67)) - Implement actor -> provider linking ([`4de853a`](https://github.com/wasmCloud/wasmCloud/commit/4de853a1d3e28126faf9efa51aaa97714af7b493)) - Exclude self from instruments ([`977260c`](https://github.com/wasmCloud/wasmCloud/commit/977260cb713f16cb2a42e4881dc4e2b5e03d481b)) - Implement update actor ([`c486dbf`](https://github.com/wasmCloud/wasmCloud/commit/c486dbf6116884da916da700b77559a8dbef9389)) - Update dependencies ([`cb86378`](https://github.com/wasmCloud/wasmCloud/commit/cb86378831e48368d31947b0a44ef39080fe6d70)) - Merge pull request #396 from rvolosatovs/feat/provider-sdk ([`6ed04f0`](https://github.com/wasmCloud/wasmCloud/commit/6ed04f00a335333196f6bafb96f2c40155537df3)) - Implement linkdef add/delete ([`e943eca`](https://github.com/wasmCloud/wasmCloud/commit/e943eca7512a0d96a617451e2e2af78718d0f685)) - Implement start and stop provider commands ([`d5beecd`](https://github.com/wasmCloud/wasmCloud/commit/d5beecd3d756a50f7b07e13afd688b2518039ee3)) - Use `wasmcloud-control-interface` ([`4e8ef11`](https://github.com/wasmCloud/wasmCloud/commit/4e8ef1103a7943a8a6c921b632093e540a7b8a1b)) - Implement actor operations ([`32cead5`](https://github.com/wasmCloud/wasmCloud/commit/32cead5ec7c1559ad0c161568712140b7d89d196)) - Implement inventory ([`0d88c28`](https://github.com/wasmCloud/wasmCloud/commit/0d88c2858ef950975bb0309bfb906881d6e8e7a6)) - Implement host stop ([`ec5675d`](https://github.com/wasmCloud/wasmCloud/commit/ec5675d11768ed9741a8d3e7c42cc1e5a823d41d)) - Implement host ping ([`239f806`](https://github.com/wasmCloud/wasmCloud/commit/239f8065b63dc5ea2460ae378840874ac660856b)) - Apply labels from environment ([`e26a5b6`](https://github.com/wasmCloud/wasmCloud/commit/e26a5b65e445d694acf3d8283cd9e80e850f8fa5)) - Introduce wasmbus lattice ([`ef20466`](https://github.com/wasmCloud/wasmCloud/commit/ef20466a04d475159088b127b46111b80a5e1eb2)) - Implement data streaming ([`7364dd8`](https://github.com/wasmCloud/wasmCloud/commit/7364dd8afae5c8884ca923b39c5680c60d8d0e3d)) - Remove `wit-deps` build scripts ([`b2c6676`](https://github.com/wasmCloud/wasmCloud/commit/b2c6676987c6879fb4fcf17066dca6c9129f63b1)) - Update WIT dependencies ([`ed4282c`](https://github.com/wasmCloud/wasmCloud/commit/ed4282c9ea1bb95e346c9a981acdc264b0fc9d3f)) - Expand parameter names ([`8bfa14f`](https://github.com/wasmCloud/wasmCloud/commit/8bfa14f0c25a9c279a12769328c4104b8ca0de74)) - Remove `wasmbus-rpc` usage ([`805f960`](https://github.com/wasmCloud/wasmCloud/commit/805f9609dbc04fd4ed8afd2447896988cbcc4ab5)) - Update dependencies ([`9ee32d6`](https://github.com/wasmCloud/wasmCloud/commit/9ee32d6fa889db105608e6df3d7533a33b26f540)) - Update `preview2-prototyping` ([`b18cd73`](https://github.com/wasmCloud/wasmCloud/commit/b18cd737a830590d232287a0ca0218357cb35813)) - Implement builtin capabilities via WIT ([`caa965a`](https://github.com/wasmCloud/wasmCloud/commit/caa965ac17eeda67c35f41b38a236f1b682cf462))
## 0.82.0 (2024-07-31) ### Chore - remove unnecessary todo comments - show provider ID on healthcheck failure messages - improve error message for forceful provider shutdown - update URLs to `wrpc` org - address clippy warnings - Bumps host version to rc.2 While I was here, I fixed the issue where we were using the host crate version instead of the top level binary host version in our events and ctl API responses - imrpove wording for spec/provider ref mismatch This commit slightly improves the wording when a provider ID and component specification URL mismatch occurs, along with specifying a possible solution. This error is thrown by `wash` and it's a bit difficult to figure out what to resolve it otherwise. - update `messaging` to `0.2.0` - remove compat crate - address clippy warnings - use `&str` directly - Use traces instead of tracing user-facing language to align with OTEL signal names - refactor component invocation tracking - remove functionality related to wasmbus invocations - update wRPC - revert incorrectly handled config conficts - remove plural actor events - integrate set-link-name and wrpc - remove unused imports/functions - remove unused function - reintroduce wasmbus over wrpc - fix `wasmcloud-host` clippy warning - update version to 0.82.0 - implement preview 2 interfaces - bump wasmcloud to 0.81 - use consistent message prefix - address clippy issue This is caused by Rust update - remove `local` host - remove support for bindle references - polish tracing and logging levels - disambiguate traced function names - improve reference parsing - add logs related to registry config - add some control interface logs - resolve 1.73.0 warnings - give NATS 2 secs to start in test - rename SUCCESS to ACCEPTED, None concurrent max - drop logging level to trace - reduce verbosity of instrumented functions - satisfy clippy linting - emit more clear start message - reduce noise from REFMAP entries - reduce noise on instruments - remove noisy fields from instruments - rename friendly noun - refactor connection opts - made fetch arg ordering consistent ### Refactor - include name with secret config - move SecretConfig into crate - address feedback, application name optional - collapse application field - efficiency, pass optional vec secrets - improve error representations, cleanup - light refactor from followup - remove extra trace_level field - improve error handling - improve error usage of bail ### Other - add secrecy - fix outdated `ctl_seed` reference ### Chore - clarify missing secret config error - fix clippy lint - update secrets integration to use the update config structure Update the secrets integration in a wasmCloud host to include information about the policy that determines which backend to communicate with. This is a change that comes in from wadm where the policy block now contains the information about which backend to use. This also passes any propertes defined on the policy to the correct backend, which are stored as a versioned string-encoded JSON object. - enable `ring` feature for `async-nats` - address clippy warnings - update to stream-based serving - improve error messages for missing links When known interfaces are accessed, we show a message that notes that the target is unknown, but we can improve on that by alerting the user to a possibly missing link. - improve error messages for missing links When known interfaces are accessed, we show a message that notes that the target is unknown, but we can improve on that by alerting the user to a possibly missing link. - downgrade link/claims log/trace - Replace actor references by component in crates Rename wash-cli wash-build tests name and references Fix nix flake path to Cargo.lock file Fix format Rename in wash-cli tests - Bump oci-distribution to 0.11.0 - generate changelogs after 1.0.1 release ### Refactor - remove redundant handler clone ### Other - document invocation handling failures ### Chore - updated with newest features ### Style - comment ### Other - check component update ref and respond with a message before task - check component image reference on component update ### Chore - replace references to 'actor' with 'component' ### Documentation - add README for the host crate ### New Features - update `wrpc:keyvalue` in providers part of this process is adopting `wit-bindgen-wrpc` in the host - update `wasi:keyvalue` - switch to `wit-bindgen-wrpc` - add label_changed event for label update/delete This commit adds a `label_changed` event that can be listened to in order to be notified of label changes on a host. The single event handles both updates and deletes. - use native TLS roots along webpki - fetch configuration direct from bucket - implement `wrpc:blobstore/blobstore` for FS - implement Redis `wrpc:keyvalue/{atomic,eventual}` - implement `wasi:http/outgoing-handler` provider - deliver full config with link - Add flags for overriding the default OpenTelemetry endpoint - Switch to using --enable-observability and --enable- flags - support pubsub on wRPC subjects Up until now, publishing and subscribing for RPC communcations on the NATS cluster happened on subjects that were related to the wasmbus protocol (i.e. 'wasmbus.rpc.*'). To support the WIT-native invocations, i.e. wRPC (#1389), we must change the publication and subscription subjects to include also the subjects that are expected to be used by wprc. This commit updates the provider-sdk to listen *additionally* to subjects that are required/used by wrpc, though we do not yet have an implementation for encode/deocde. - include actor_id on scaled events - downgrade provider claims to optional metadata - downgrade actor claims to optional metadata - Glues in named config to actors This introduces a new config bundle that can watch for config changes. There is probably a way to reduce the number of allocations here, but it is good enough for now. Also, sorry for the new file. I renamed `config.rs` to `host_config.rs` so I could reuse the `config.rs` file, but I forgot to git mv. So that file hasn't changed - implement AcceptorWithHeaders - implement wasmcloud_transport wrappers - implement `wrpc:http/incoming-handler` - begin incoming wRPC invocation implementation - switch to `wrpc` for `wasmcloud:messaging` - switch to `wrpc:{keyvalue,blobstore}` - implement `wrpc:http/outgoing-handler.handle` - support component invoking polyfilled functions - change set-target to set-link-name Up until the relatively low-level `wasmcloud:bus/lattice` WIT interface has used a function called `set-target` to aim invocations that occurred in compliant actors and providers. Since wRPC (#1389) enabled wasmCloud 1.0 is going to be WIT-first going forward, all WIT-driven function executions have access to the relevant interface (WIT interfaces, rather than Smithy-derived ones) that they call, at call time. Given that actor & provider side function executions have access to their WIT interfaces (ex. `wasi:keyvalue/readwrite.get`), what we need to do is differentiate between the case where *multiple targets* might be responding to the same WIT interface-backed invocations. Unlike before, `set-target` only needs to really differentiate between *link names*. This commit updates `set-target` to perform differentiate between link names, building on the work already done to introduce more opaque targeting via Component IDs. - remove module support - add invocation and error counts for actor invocations Add two new metrics for actors: * the count of the number of invocations (`wasmcloud_host.actor.invocations`) * the count of errors (`wasmcloud_host.actor.invocation.errors`) * the lattice ID * the host ID * provider information if a provider invoked the actor: ** the contract ID ** the provider ID ** the name of the linkdef 1. We have been needing something like this for a while, at the very least for being able to configure link names in an actor at runtime 2. There aren't currently any active (yes there were some in the past) efforts to add a generic `wasi:cloud/guest-config` interface that can allow any host to provide config values to a component. I want to use this as a springboard for the conversation in wasi-cloud as we will start to use it and can give active feedback as to how the interface should be shaped - make claims optional (at least for now) - add streaming support to `wasmcloud:bus` - rename `wasmcloud_host` -> `wasmcloud_runtime` - remove all `wasmcloud-interface-*` usages - add support for `command` executables (I/O actors) - add local lattice proving the concept, which is used for testing of the feature - implement an actor instance pool - generate crate changelogs - limit max execution time to 10 minutes - update to Wasmtime 20 - generate crate changelogs - count epoch in a separate OS thread - handle invocations in tasks - propagate `max_execution_time` to the runtime - add Host level configurability for max_execution_time by flag and env variables - Introduce humantime::Duration for capturing human readable input time. - Add the `--max-execution-time` flag (alias: --max-time) to wasmcloud binary and wash up command, allowing for configuration of the max execution time for the Host runtime. - Set Default to 10min and Time format to Milliseconds. ### Bug Fixes - remove publish_event from stop_actor - differentiate no config and config error - allow overwriting provider reference - warn scaling with different imageref - rename scaled ID from actor to component - Don't clone targets with handlers This is a fix that ensures each component has its own set of link name targets. Before this, it was sharing the whole set of link names between all running component instances (of each individual component). - deliver target links to started provider - fix `link_name` functionality, reorganize tests - correct name and data streaming, update WIT - Recreates polyfill imports on update This fixes an issue where if you add a new custom interface to an actor when updating it, it would fail to have the imports in place - fix deadlock and slow ack of update - flatten claims response payload - race condition with initial config get - improve target lookup error handling - update wrpc_client - re-tag request type enum policy - instrument handle_invocation and call - Fixes write lock issue on policy service Our policy decision logic was taking a write lock even when reading the queue. This basically treated it like a mutex and slowed down the number of requests we could handle. - encode custom parameters as tuples - correctly invoke custom functions - bindgen issues preventing builds This commit fixes the provider bindgen issues for non http-server builds (ex. kv-redis) - set log_level for providers - fix clippy warning, added ; for consistency, return directly the instance instead of wrapping the instance's components in a future - Add comments, remove useless future::ready - fmt - add subject to control interface logs - publish claims with actor_scaled - override previous call alias on clash - update format for serialized claims - disable handle_links trace until wadm sends fewer requests - queue subscribe to linkdefs and get topics - drop problematic write lock - publish correct number of actor events - stop sending linkdef events on startup - change expected host label prefix to remove collision with WASMCLOUD_HOST_SEED - fixes #746 - return an InvocationResponse when failing to decode an invocation - deprecate HOST_ label prefix in favor of WASMCLOUD_HOST_ - download actor to scale in task - proxy RUST_LOG to providers - rework host shutdown - Always include a timeout for graceful shutdown (e.g. if NATS connection dies, it will never finish) - running the docker compose for o11y - (re) building dog-fetcher - modifying the WADM w/ dog fetcher (done by this commit) - build & create PAR for http-client - build & create PAR for http-server - set WASMCLOUD_OVERRIDE_TRACES_ENDPOINT before `wash up` - replacing existing wasmcloud host (in `~/.wash/downloads/v1.0.2`) ### Other - expect stop_actor function parameter host_id to be unused - update `wrpc-interface-http` - update wRPC - update wRPC - update to wasmtime 17 - 'upstream/main' into `merge/wash` - bump crate versions - bump to `0.79.0` - update dependencies - bump version to `0.78.0` - update dependencies - remove `wit-deps` build scripts - update WIT dependencies - update dependencies - update `preview2-prototyping` ### Refactor - Actor -> Component - move wasmcloud wrpc transport client to core This commit moves the wasmcloud-specific wrpc transport client to the `wasmcloud-core` crate. From here, it can be used by both the host (`wasmbus`) and other places like tests. - move label parsing out of host library - remove deprecated code related to start actor cmd - rename label to key - drop write locks immediately - remove unnecessary mut - remove instance pooling - implement `ResourceRef::authority` - introduce artifact fetchers - derive `Default` for `Auth` - rename `RegistrySettings` -> `RegistryConfig` - rework fetching logic - be explicit about `async_nats` imports - reduce verbosity on actor logs - flatten optional annotations to always be set - construct a strongly typed HostData to send to providers - establish NATS connections concurrently - use `wasmcloud-compat` structs - remove unnecessary allocations - create bucket explicitly instead of stream This also gracefully handles errors where the bucket has already been provisioned with custom settings, allowing multiple hosts to run in the same pre-provisioned lattice - exclude self from instruments - use `wasmcloud-control-interface` - expand parameter names - remove `wasmbus-rpc` usage ### Style - address nits - use skip_all - replace needs_chunking function with direct comparison - move longer fields to their own lines - update imports - satisfy clippy - stop unnecessarily satisfying clippy - remove constants - rename most instances of lattice and wasmbus to host - use context ### Chore (BREAKING) - remove cluster_seed/cluster_issuers - rename ctl actor to component - update ctl to 0.31.0 ### New Features (BREAKING) - Removes old guest config and uses runtime config instead Most of the changes are related to wit updates, but this removes the guest config from `wasmcloud:bus` and pulls down `wasi:config` in its place - rename actor_scale* events - remove capabilities - Adds version to control API This should be the final breaking change of the API and it will require a two phased rollout. I'll need to cut new core and host versions first and then update wash to use the new host for tests. - convert to `wrpc:blobstore` - use `wasmcloud:messaging` in providers Also implement statically invoking the `handler` on components in the host - start providers with named config - refactor componentspec, deliver links to providers - cache request by unique data - formalize policy service - wrap all ctl operations in CtlResponse - remove collection type aliases - flatten instances on actor/providers - fully support interface links, remove aliases - support wrpc component exports - support interface link put, component spec - Changes config topic to be for named config This is the first in a set of changes to move over to named config. It is not technically complete as you essentially have to name your config the same as the actor ID. I did this purposefully so as to not have a PR of doom with all the changes. The next PR will be adding named config to the scale command, then support for named config and providers in another PR after that - Updates topics to the new standard This is a wide ranging PR that changes all the topics as described in #1108. This also involved removing the start and stop actor operations. While I was in different parts of the code I did some small "campfire rule" cleanups mostly of clippy lints and removal of clippy pedant mode. - add heartbeat fields to inventory - change heartbeat payload to inventory - remove singular actor events, add actor_scaled - upgrade max_instances to u32 - rename max-concurrent to max-instances, simplify scale - use max concurrency instead of count - validate invocations for antiforgery and claims - implement provider health checks - implement structured logging - respect allow_file_load - enforce rpc_timeout - implement rpc,ctl,prov_rpc connections - use allow_latest and allowed_insecure config - use js_domain provided by cli - implement graceful provider shutdown delay - maintain cluster issuers list - encrypt link secrets, generate xkeys for providers - configure observability with trace_level option - add secrets backend topic flag ### Bug Fixes (BREAKING) - consistent host operations - remove support for prov_rpc NATS connection ### Refactor (BREAKING) - rename lattice prefix to just lattice - make content_length a required field Add support for supplying additional CA certificates to OCI and OpenTelemetry clients fetch secrets for providers and links add secrets handler impl for strings set NATS queue group conflate wasi:blobstore/container interface with blobstore pass original component instance through the context upgrade wrpc, async-nats, wasmtime support ScaleComponentCommand w/ update allow empty payloads to trigger stop_host add link name to wRPC invocationsThis commit adds the “link-name” header to invocations performed bythe host using wRPC. Add support for configuring grpc protocol with opentelemetry Updates host to support new wasm artifact typeThis change is entirely backwards compatible as it still supports theold artifact type. I did test that this can download old and newmanifest types gracefully shutdown epoch interrupt thread pass policy string directly to backend use name instead of key for secret map skip backwards-compat link with secret check provided secrets topic for non-empty setup debug tracesThis commit contains experimental code used to debug/replicate theo11y traces for making a call with http-client & http-provider.Running this requires the following hackery: propagate traces through components ## v0.18.2 (2021-05-13) ## v0.18.1 (2021-04-29) ## v0.18.0 (2021-04-16) ## v0.17.0 (2021-04-13) ## v0.16.1 (2021-04-09) ## v0.16.0 (2021-03-26) ## v0.15.5 (2021-03-23) ## v0.15.4 (2021-03-22) ## v0.15.3 (2021-03-05) ## v0.15.1 (2021-03-01) ## v0.15.0 (2021-02-16)