You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More a feature request than a problem... raising following a conversation in MacAdmins Slack
GitHubReleasesInfoProvider does not raise a warning or error if a repo has been archived or disabled. If the media is still available, recipes will complete successfully, and admins have no way of knowing the project state unless there is a manual check.
Preferences contents
N/A
AutoPkg output
N/A
Expected behaviour
If GitHubReleasesInfoProvider detects that a repo is either "archived": true, or "disabled": true, it should raise a warning to inform the admin that investigation is need.
Version (please complete the following information):
OS version: N/A
AutoPkg Version: N/A
The text was updated successfully, but these errors were encountered:
if the repo is archived or disabled, the processor should fail by default;
allow an input variable to override that behavior and ignore the archive/disable flag and use it anyway
It's still potentially useful to run an autopkg recipe against an old repo, just to simplify the effort of manually importing a software release from it. So admins who wish to do so can intentionally opt-in via their override.
Describe the problem
More a feature request than a problem... raising following a conversation in MacAdmins Slack
GitHubReleasesInfoProvider
does not raise a warning or error if a repo has been archived or disabled. If the media is still available, recipes will complete successfully, and admins have no way of knowing the project state unless there is a manual check.Preferences contents
N/A
AutoPkg output
N/A
Expected behaviour
If
GitHubReleasesInfoProvider
detects that a repo is either"archived": true,
or"disabled": true,
it should raise a warning to inform the admin that investigation is need.Version (please complete the following information):
The text was updated successfully, but these errors were encountered: