Skip to content

docs: design document for Updates #242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
paullatzelsperger wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: design document for Updates #242

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fd8f5a8
docs: design update activity
paullatzelsperger Nov 13, 2026
a346a86
docs: design update activity 2
paullatzelsperger Nov 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/developer/architecture/provisioning/orchestrator.design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,7 +198,7 @@ facilitate the creation of activity agents. The framework is built on the core m
as the HTTP Client and Router to be used. An agent is instantiated by passing a configuration to the NATS agent
launcher:

```
```go
package launcher

import (
Expand All @@ -222,7 +222,7 @@ to instantiate the `ActivityProcessor` implementation.

The following is an example of an activity agent configuration:

```
```go
package launcher

import (
Expand Down Expand Up @@ -269,7 +269,7 @@ Activities model resource lifecycles. For example, a resource may be deployed an
desirable to require separate agents for each resource lifecycle operation. Activity processors can use the
`discriminator` property to distinguish between different resource lifecycle states:

```
```go
package example

import "github.com/eclipse-cfm/cfm/pmanager/api"
Expand Down Expand Up @@ -313,4 +313,4 @@ API.

The Orchestrator can integrate with infrastructure provisioning technologies such
as [Eclipse Symphony](https://github.com/eclipse-symphony/symphony), [Fulcrum](https://github.com/fulcrumproject),
and [Liqo](https://liqo.io/) via `ActivityProcessor` implementations.
and [Liqo](https://liqo.io/) via `ActivityProcessor` implementations.
Loading
Loading