Closed lbussell closed 1 month ago
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.
Applying the RegistryOverrideOptions
class to other commands is proving to be really involved and not really worth the ROI, so I'm going to stop that.
I am taking suggestions for other tests I could implement, but this command is pretty simple. So I think this is ready to review.
For some reason when running ImageBuilder's help command, this command shows up at the bottom while the others are in alphabetical order:
Commands:
annotateEolDigests <EolDigestsListPath> <AcrName> <RepoPrefix> <AnnotationDigestsOutputPath>
build
cleanAcrImages <RepoName> <Subscription> <ResourceGroup> <RegistryName>
<snip>
waitForMcrDocIngestion <CommitDigest>
waitForMcrImageIngestion <ImageInfoPath>
generateSigningPayloads <ImageInfoPath> <PayloadOutputDirectory>
For some reason when running ImageBuilder's help command, this command shows up at the bottom while the others are in alphabetical order:
Oh, it must be because I put it in a separate namespace...
Changes:
GenerateSigningPayloads
OrasSerivce
->LifecycleMetadataService
- since it contains "business logic" I think those methods should live outside the ORAS client class. For some reason Git did not pick those up as renames.OrasClient
which only talks to ORAS CLIExecuteHelper
methodsTodo:
not sure how those manifest in the image info file - will this even be important if we only use digests in this command