After the test is fixed, it will have to be re-enabled in the sharding_auth, sharding_auth_audit, sharding_update_v1_oplog, etc. suites from which it has been disabled as a part of SERVER-58295.

So we should have to make changes only to the yml file for the above suites, along with the actual bug fix itself. This test has currently been added to the "exclude_files" section of all the suites.

Also, please see SERVER-58351, which tracks all the disabled sharding tests that need to be completely re-enabled / deleted eventually (i.e. the "disabled_due_to_server_58295" tag needs to be removed from the test).