Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Is this not something we can get from the package data?
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.
@tas50 yes but then we have to provide the customer a list of packages.
this case is easy
the version of the exchange version is 15.1.2507.6
but there exists cases where the version of the Exchange server differs from the Version of the Cumulative Update, like this case:
the version of the exchange version is 15.2.1544.9.
but then there are installation which no Cumulative Update is installed
@tas50 do you prefer this query:
packages.where(name == /Exchange Server.*Cumulative Update.*/ || name == 'Microsoft Exchange Server') { name version }
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't get the data correctly with package then this makes sense. Just double checking