Skip to content
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.

FIX: CCV does not publish on update when component is set to "latest" #66

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arusso
Copy link

@arusso arusso commented Apr 26, 2019

When a CCV has a component that is set to latest in Satellite and also the cvmanager configuration, cvmanager is unable to detect version changes and the CCV will not be published.

This PR resolves this issue by comparing the component versions as they were in the last published version of the CCV rather than the last configured version of the CCV (which when set to latest in Satellite, will always be the latest version).

@mccun934
Copy link

mccun934 commented Aug 7, 2019

@arusso this change looks good, I'd be happy to give a test. Mind git squashing these commits into one?

@arusso arusso force-pushed the ccv-update-publish-fix branch from 473ff31 to 51120fb Compare August 7, 2019 21:21
@pcfe
Copy link

pcfe commented Nov 23, 2019

LGTM

note to self; remember to allow, if needed, out of order LCE target with:

:settings:
  :force: true

@arusso
Copy link
Author

arusso commented Nov 26, 2019

Let me know if there's something I still need to do to help get this merged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants