- 
                Notifications
    You must be signed in to change notification settings 
- Fork 34
ACM-5068: Set consolidateManifests=false when orderManifests=true #128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACM-5068: Set consolidateManifests=false when orderManifests=true #128
Conversation
| There were some unrelated unit tests failing when I was testing, will check back to see if this is consistent. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall to me!
        
          
                internal/ordering_test.go
              
                Outdated
          
        
      | wantErr: "extraDependencies may not be set in policy one manifest[0] because orderManifests is set", | ||
| }, | ||
| "orderManifests and consolidateManifests is false": { | ||
| "orderManifests is true and consolidateManifests is unset": { | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: can we add a tiny bit more context to these tests?
| "orderManifests is true and consolidateManifests is unset": { | |
| "orderManifests is true in policyDefaults, and consolidateManifests is unset": { | 
        
          
                internal/ordering_test.go
              
                Outdated
          
        
      | wantFile: "testdata/ordering/three-ordered-manifests.yaml", | ||
| wantErr: "", | ||
| }, | ||
| "orderManifests in policy and consolidateManifests is false": { | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we can update this description as well, something like
| "orderManifests in policy and consolidateManifests is false": { | |
| "orderManifests is true in policy and consolidateManifests is unset": { | 
Simple checks added on conditionals for both default and actual values to change consolidateManifests=false Signed-off-by: Jeffrey Luo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| [APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JeffeyL, JustinKuli The full list of commands accepted by this bot can be found here. The pull request process is described here 
Needs approval from an approver in each of these files:
 
 Approvers can indicate their approval by writing  | 
Description: (Copied from issue) When using the Policy Generator, when
orderManifestsistrue, it's a signal that the user wants to have dependencies set for the manifests within. However,consolidateManifestsdefaults totrue, soorderManifestswon't really do anything unlessconsolidateManifestsis also set to false. As a convenience, we should setconsolidateManifestsaccordingly so that this implementation detail is abstracted for the user.Solution: Conditionals were added where
consolidateManifestswas being set (both default and actual values) to set tofalsewhen the correspondingorderManifestsvalue istrue.Ref: https://issues.redhat.com/browse/ACM-5068