microsoft / microsoft/CSS-Exchange

Show script version before update

Open
#2,104 0 comments 0 reactions 1 assignee View on GitHub

@dpaulson45 is already working on this.

Since Dec 6, 2024.

Enhancement good first issue P2 Shared Function Work Item
Dominant language
PowerShell
Stars
1.3k
Forks
395
Avg merge
14h 7m
Merged PRs (30d)
5

Description

Hi,

Currently, when we run the script and if an update is needed, then it asks confirmation to update but doesn't show the current (nor the updated version).

It would be very convenient to see the current script version before doing an update. It would help seeing how far behind the script is from the latest version.

Currently, it shows:

[PS] C:\temp>.\HealthChecker.ps1

Confirm
Are you sure you want to perform this action?
Performing the operation "Update script to latest version" on target "HealthChecker.ps1".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):
File signed by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
AutoUpdate: Signature validated.
AutoUpdate: Succeeded.
Script was updated. Please rerun the command.
Do you like the script? Visit https://aka.ms/HC-Feedback to rate it and to provide feedback.


It could show the following (current version + updated version) :

[PS] C:\temp>.\HealthChecker.ps1

+ Exchange Health Checker version 24.06.13.2304

Confirm
Are you sure you want to perform this action?
Performing the operation "Update script to latest version" on target "HealthChecker.ps1".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):
File signed by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
AutoUpdate: Signature validated.
AutoUpdate: Succeeded.
Script was updated to version

+ xx.xx.xx.xxxx (new version number)

Please rerun the command.
Do you like the script? Visit https://aka.ms/HC-Feedback to rate it and to provide feedback.


Thank you

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.