You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature: Add only filters for local OS and cluster architecture component filtering (zarf-dev#591)
* add Only filters for components
* start describing the schema better
* Add only filter to docs
* add compose debug messages and handle bad component name
* Add debug message to component compatibility test
Copy file name to clipboardexpand all lines: docs/4-user-guide/2-zarf-packages/1-zarf-packages.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@ sidebar_position: 1
4
4
5
5
# Understanding Zarf Packages
6
6
7
-
A Zarf package is a single binary Tarball that contains everything you need to deploy a system or capability while fully disconnected. Zarf packages are defined by a `zarf.yaml` file.
7
+
A Zarf package is a single tarball archive that contains everything you need to deploy a system or capability while fully disconnected. Zarf packages are defined by a `zarf.yaml` file.
8
8
9
-
Zarf packages are built while 'online' and connected to whatever is hosting the dependencies your package definition defined. When being built, all these defined dependencies are pulled from the internet and stored within the tarball package. Because all the dependencies are now within the tarball, the package can be deployed on to disconnected systems that don't have connection to the outside world.
9
+
Zarf packages are built while 'online' and connected to whatever is hosting the dependencies your package definition defined. When being built, all these defined dependencies are downloaded and stored within the archive. Because all the dependencies are now within the tarball, the package can be deployed on to disconnected systems that don't have connection to the outside world.
10
10
11
11
The `zarf.yaml` file, that the package builds from, defines declarative instructions on how capabilities of the package should be deployed. The declarative nature of the package means everything is represented by code and automatically runs as it is configured, instead of having to give manual steps that might not be reproducible on all systems.
0 commit comments