Was there a user request?

Including the flag in the build policy seems entirely correct regardless and really is an oversight in the original PR. So we should do that regardless. Will file PR momentarily.

If we wanted to go further, perhaps an 'EnableDraft' hub setting defaulting to True, similar to 'EnableMaven'. This would be checked:

• in new_build, blocking any new draft imports
• in import_build, blocking completion of any in-progress draft builds
• in _direct_tag_build, blocking tagging (but not untagging)

So, this is functionally equivalent to setting strict draft block rules in the build policy and tag policy, but it's just one setting instead of a policy rule. Also there are ways to get around policy.

When denied, we should call reject_draft for consistency.
(other import pathways already deny it)

Note that we should not block untagging. It's possible that an admin might disable the feature but still have some existing draft builds that they might want to untag (and we wouldn't want the gc to fail on such either).

More just a note for me during discussion with @kevin on matrix. Question is if it can be disabled before Fedora agree on workflow/usage of this.

I think, that the #4015 is sufficient for now. If anyone will request more strict disabling, we can revisit it.

Commit dd128f86 relates to this ticket

Commit ecd5d960 relates to this ticket

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/4014

Please continue any further discussion there.