Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Look into an Update mode. Together with a major change of how HealOps and HealOpsPackages are updated. #20

Open
larssb opened this issue Aug 19, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@larssb
Copy link
Owner

larssb commented Aug 19, 2018

The idea is:
-> Have one update job on a node running HealOps. This job will run everything related to updating HealOps and HealOpsPackages.
-> Or have a job that updates HealOps and the jobs that executes a *.Tests.ps1 file in a HealOpsPackage will look for updates to the HealOpsPackage.

Benefits:

  • A potential simpler way of updating. And the scenarios involved therein.
  • Seperation of concerns. Normally a good road to follow when implementing/developing software.
    --> One UpdateMode
    --> One ReportMode
    --> One StatsMode

Potential issues:

  • Invoke-HealOps could already be running. So issues with locks & so forth. Think about this really is a issue or not. Only an issue if the one for all Update job way is chosen.
@larssb larssb added the enhancement New feature or request label Aug 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant