Enable Agents Checkboxes not applying to EDF's

[Cubert]

The first part, should not happen unless something changes in the EDFs to cause the Enable Source box to be empty or (False).

Screenshot 2024-08-29 095322.png (13.41 KiB) Viewed 4601 times

I am not sure why that would disapear, I do not have anything in place that I am aware of that clears these fields. Let me go have a look at the full path a sourced agent traverses to see what might trigger such an event.

As for the ProGet repo, can you post your sources list from the agent in question. What I am looking for is the number of repos in list and their priorities.

[Cubert]

Ok, found the misterious source removal.

During agent scans we operate a few test first to see if agent need to be cleaned up. One of these tests happens if a source policy is removed from the master list of source policies, any agents on next scan, if they belonged to the policy that now is non existant, will be cleared out and reset back to the default repo.

We had an error in the test that caused agents to be cleared when they shouldn't be. This error really didn't be come apparent till build 1.0.0.16 where the new Chocolatey Default Repo reset was added. This function responds to any change in source policy, changing the agents current source back to the default repo.

---1.0.0.16---
Added Policy Editor and added Chocolatey Default Repo reset.

I have resolved this issue in build 1.0.0.23

https://delivery.shopifyapps.com/-/6a0a ... 3732a7a03b


I am on the fence for changing the Source deployment script to remove all sources but the source you provide in the policy.
Please post your thoughts on this, what would you expect the policy to do? Should we force the source policy repo only?

[Cubert]

Did you have a chance to let things run now that your sources issue should be resolved?