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
[confcom] supporting OCI images and adding tests (#8570)
* adding fragment signing tests
* fixing where params and vars are filled in
Co-authored-by: Khalil Sayid <khalilsayid@microsoft.com>
* updating docs to explain types of fragments
Co-authored-by: Khalil Sayid <khalilsayid@microsoft.com>
* fixing error that came up when using diff mode with non-default fragments
* adding logging to some functions
* adding support for OCI formatted images
* adding exec process section to config file
* adding support for custom mount options
---------
Co-authored-by: Khalil Sayid <khalilsayid@microsoft.com>
## Microsoft Azure CLI 'confcom acipolicygen' Extension Examples
@@ -192,6 +194,8 @@ Use the following command to generate CCE policy for the image.
192
194
az confcom acipolicygen -a .\sample-template-input.json --tar .\file.tar
193
195
```
194
196
197
+
Note that multiple images saved to the tar file is only available using the docker-archive format for tar files. OCI does not support multi-image tar files at this time.
198
+
195
199
Example 12: If it is necessary to put images in their own tarballs, an external file can be used that maps images to their respective tarball paths. See the following example:
196
200
197
201
```bash
@@ -665,6 +669,15 @@ Run `az confcom acifragmentgen --help` to see a list of supported arguments alon
665
669
666
670
For information on what a policy fragment is, see [policy fragments](#policy-fragments). For a full walkthrough on how to generate a policy fragment and use it in a policy, see [Create a Key and Cert for Signing](../samples/certs/README.md).
667
671
672
+
### Types of Policy Fragments
673
+
674
+
There are two types of policy fragments:
675
+
676
+
1. Image-attached fragments: These are fragments that are attached to an image in an ORAS-compliant registry. They are used to provide additional security information about the image and are to be used for a single image. Image-attached fragments are currently in development. Note that nested image-attached fragments are *not* supported.
677
+
2. Standalone fragments: These are fragments that are uploaded to an ORAS-compliant registry independent of a specific image and can be used for multiple images. Standalone fragments are currently not supported. Once implemented, nested standalone fragments will be supported.
678
+
679
+
### Examples
680
+
668
681
**Examples:**
669
682
670
683
Example 1: The following command creates a security fragment and prints it to stdout as well as saving it to a file `contoso.rego`:
0 commit comments