Separating applications from the module #236
Replies: 1 comment 1 reply
-
Maybe check for updated manifests / functions when the module is loaded? I have done this in the .psm1 file for instance. Many of us use the module in automated processes which means the module gets loaded each run, which for me would be a perfect time to check for updates. If you're introducing the If you do decide to go this way, please let the function decide if it's running the module elevated or not. If elevated |
Beta Was this translation helpful? Give feedback.
-
I've been thinking about how to seperate the applications (manifests and internal functions) from the module so that an update to an application isn't tied to an update to the module.
At this point, I have an idea that I'd write
Update-EvergreenApp
or similar which would download the internal functions and manifests from the repo into a local directory (e.g.,C:\ProgramData\Evergreen
).Can anyone see an issue with this approach or think of a better solution?
Beta Was this translation helpful? Give feedback.
All reactions