what is the best practice for updating custom powershell modules

This topic contains 2 replies, has 2 voices, and was last updated by Profile photo of Luis Yax Luis Yax 1 year, 8 months ago.

  • Author
  • #28125
    Profile photo of Luis Yax
    Luis Yax

    Hi All,

    I just started creating my custom modules that I'm planning to deploy.

    What is your best custom practice for getting the latest code?

    I was thinking along the lines of getting the the hash of the master file and if it does't match my copy, to update it

    Any suggestions?


  • #28126
    Profile photo of Don Jones
    Don Jones

    You're meant to provide a manifest that includes a version. That way you can simply check the version, and even have scripts define a specific version dependency, if desired. Ideally, you'd have your module in a repo that PowerShellGet can access, so you can easily check the repo version and update if needed.

    However, checking a file hash is an approach that would probably work.

  • #28128
    Profile photo of Luis Yax
    Luis Yax

    Don, i'll start looking at the manifest option.


You must be logged in to reply to this topic.