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
When I provide the jfrog-cli with a spec.json using the command "jf ds rbc --spec=spec.json test_rb 1.0.0" { "files": [{ "pattern": "some-repo-local/path/image/1.36.0/manifest.json", "target": "target-edge-repo/" }] }
Then it collects the layers from the manifest.json but I dont have control over the mappings of the layers due to working with “pattern” and not “aql” where I can specifically define it.
Thus, In order to workaround it I modify the spec.json to be like this: { "files": [{ "pattern": "some-repo-local/(path/image/1.36.0/*)", "target": "target-edge-repo/{1}" }] }
That way it collects the layers from the original path and not by reading the manifest.json and including its layers.
The thing is that distribution service has an OOTB feature which parse the manifest.json and includes all the layers of the image in the rb once it identifies that a manifest.json is given in the AQL, but when we use the "pattern" attribute, we dont have a way to control the mappings of those layers incase we want to distribute them to the edge in a specified repo.
Is it something planned to be supported? or it enough to work with the groupings in the pattern () and {1}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When I provide the jfrog-cli with a spec.json using the command "jf ds rbc --spec=spec.json test_rb 1.0.0"
{ "files": [{ "pattern": "some-repo-local/path/image/1.36.0/manifest.json", "target": "target-edge-repo/" }] }
Then it collects the layers from the manifest.json but I dont have control over the mappings of the layers due to working with “pattern” and not “aql” where I can specifically define it.
Thus, In order to workaround it I modify the spec.json to be like this:
{ "files": [{ "pattern": "some-repo-local/(path/image/1.36.0/*)", "target": "target-edge-repo/{1}" }] }
That way it collects the layers from the original path and not by reading the manifest.json and including its layers.
The thing is that distribution service has an OOTB feature which parse the manifest.json and includes all the layers of the image in the rb once it identifies that a manifest.json is given in the AQL, but when we use the "pattern" attribute, we dont have a way to control the mappings of those layers incase we want to distribute them to the edge in a specified repo.
Is it something planned to be supported? or it enough to work with the groupings in the pattern () and {1}
Beta Was this translation helpful? Give feedback.
All reactions