Skip to content

Adding content from RHEM upstream to chapter 7 (#3340) #3361

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

Merged
merged 1 commit into from
Apr 29, 2025
Merged

Adding content from RHEM upstream to chapter 7 (#3340) #3361

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions downstream/assemblies/platform/assembly-edge-manager-manage-apps.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,11 @@ The {RedHatEdge} supports the `podman-compose` tool as the application runtime a
* You must install the {RedHatEdge} CLI.
* You must log in to the {RedHatEdge} service.
* Your device must run an operating system image with the `podman-compose` tool installed.

For more information, see xref:edge-manager-build-bootc[Building a _bootc_ operating system image for use with the {RedHatEdge}].

include::platform/proc-edge-manager-build-app-packages.adoc[leveloffset=+1]

include::platform/ref-edge-manager-specify-apps-inline.adoc[leveloffset=+1]

include::platform/proc-edge-manager-deploy-apps.adoc[leveloffset=+1]
44 changes: 44 additions & 0 deletions downstream/modules/platform/ref-edge-manager-specify-apps-inline.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
[id="edge-manager-specify-apps-inline"]

= Specify applications inline in the device specification

Application manifests are specified inline in a device's specification, so you do not need to build an OCI registry application package.

The inline application provider accepts a list of application content with the following parameters:

|===
| Parameter | Description
| Path | The relative path to the file on the device. Note that any existing file is overwritten.
| Content (Optional) | The plain text (UTF-8) or base64-encoded content of the file.
| ContentEncoding | How the contents are encoded. Must be either "plain" or "base64". Defaults to "plain".
|===

.Example

[source,yaml]
----
apiVersion: flightctl.io/v1alpha1
kind: Device
metadata:
name: some_device_name
spec:
[...]
applications:
- name: my-app
appType: compose
inline:
- content: |
version: "3.8"
services:
service1:
image: quay.io/flightctl-tests/alpine:v1
command: ["sleep", "infinity"]
path: podman-compose.yaml
[...]
----

[NOTE]
====
Inline compose applications can have two paths at most.
You must name the first one `podman-compose.yaml`, and the second (override) `podman-compose.override.yaml`.
====