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] Adding standalone fragment support (#9097)
* ensure that oras discover doesn't error when the remote image doesn't exist
* updating version
* adding print for binary version
* commenting out some tests due to docker incompatibility
* pull image before saving to tar
---------
Co-authored-by: Heather Garvison <[email protected]>
Copy file name to clipboardExpand all lines: src/confcom/azext_confcom/README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -866,6 +866,18 @@ Using the same command, the default mounts and environment variables used by VN2
866
866
az confcom acifragmentgen --input ./fragment_config.json --svn 1 --namespace contoso
867
867
```
868
868
869
+
Example 6: Create an import statement from a signed fragment in a remote repo:
870
+
871
+
```bash
872
+
az confcom acifragmentgen --generate-import --fragment-path contoso.azurecr.io/<my-fragment>:v1 --minimum-svn 1
873
+
```
874
+
875
+
This is assuming there is a standalone fragment present at the specified location of `contoso.azurecr.io/<my-fragment>:v1`. Fragment imports can also be created using local paths to signed fragment files such as:
876
+
877
+
```bash
878
+
az confcom acifragmentgen --generate-import --fragment-path ./contoso.rego.cose --minimum-svn 1
879
+
```
880
+
869
881
## Microsoft Azure CLI 'confcom katapolicygen' Extension Examples
870
882
871
883
Run `az confcom katapolicygen --help` to see a list of supported arguments along with explanations. The following commands demonstrate the usage of different arguments to generate confidential computing security policies.
Copy file name to clipboardExpand all lines: src/confcom/azext_confcom/_help.py
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -165,7 +165,7 @@
165
165
166
166
- name: --fragment-path -p
167
167
type: string
168
-
short-summary: 'Path to an existing policy fragment file to be used with --generate-import. This option allows you to create import statements for the specified fragment without needing to pull it from an OCI registry'
168
+
short-summary: 'Path to an existing signed policy fragment file to be used with --generate-import. This option allows you to create import statements for the specified fragment without needing to explicitly pull it from an OCI registry. This can either be a local path or an OCI registry reference. For local fragments, the file will remain in the same location. For remote fragments, the file will be downloaded and cleaned up after processing'
Copy file name to clipboardExpand all lines: src/confcom/azext_confcom/_params.py
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -172,7 +172,6 @@ def load_arguments(self, _):
172
172
required=False,
173
173
help="Omit the id field in the policy. This is helpful if the image being used will be present in multiple registries and used interchangeably.",
174
174
)
175
-
176
175
c.argument(
177
176
"include_fragments",
178
177
options_list=("--include-fragments", "-f"),
@@ -266,7 +265,7 @@ def load_arguments(self, _):
266
265
"fragment_path",
267
266
options_list=("--fragment-path", "-p"),
268
267
required=False,
269
-
help="Path to a policy fragment to be used with --generate-import to make import statements without having access to the fragment's OCI registry",
268
+
help="Path to a signed policy fragment to be used with --generate-import to make import statements without having access to the fragment's OCI registry. This can either be a local path or a registry address.",
0 commit comments