Closed bparees closed 3 years ago
@ecordell @kevinrizza @gallettilance @jmccormick2001 ptal
@kevinrizza @gallettilance @njhale @ecordell i've updated this based on our convos:
1) mutation is done during opm add, not listbundles 2) if a bundle has skipranges, then additional skips are added so that rebuilds are covered 3) clearly spells out adding a new substitutes-for column to the existing operatorbundle table 4) i still have this adding a new first class field to the CSV. I guess we can still debate if it's better suited for the properties map.
i think that is all the open issues from the last round of discussion/review but if i've missed something please let me know.
New changes are detected. LGTM label has been removed.
This field will allow dynamic stitching in of upgrade paths where existing skips/replaces references can also be applied to bundles which "substitute-for" the bundle that was originally referenced.