Story #3778: [Epic] As a user, I can run Pulp 3 in a FIPS-enabled environment
As a user, I'm prevented from changing ALLOWED_CONTENT_CHECKSUMS if I already have content in my DB
Users should not change the
ALLOWED_CONTENT_CHECKSUMS if they already have content in their DB.
Let's add a check at Pulp start time that causes them to not do that
As suggested by @daviddavis, at the bottom of the pulpcore.app.settings, add another check that performs a select like SELECT * FROM artifacts WHERE a IS NULL or b IS NULL ... and if this returns any artifacts, raise an ImproperlyConfigured error.
Since we can't change settings during functional test runs, we cannot reasonably test for this.
Updated by daviddavis about 3 years ago
- Status changed from MODIFIED to ASSIGNED
- Sprint/Milestone deleted (
This causes a bug in pclean where a database session gets created and thus the db cannot be dropped. Reverting and removing from 3.7: