Revert "Merge branch '214607-ci-jwt-signing-key/check' into 'master'"
What does this MR do?
We had #214607 (closed) reverted (see gitlab-com/gl-infra/production#2284 (closed)) but meanwhile we got !33920 (merged) merged. The later is a complementary to the former and adds a check to the gitlab:check rake task. While it's (most likely) OK to have it, it makes no sense to keep it until we sort out the root issue with #214607 (closed).
This MR reverts !33920 (merged) to get rid of this check.
In the context of gitlab-com/gl-infra/production#2284 (closed) it's questionable how useful will such check be anyway, given it will run on just one node (where the rake task is executed).
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
/label Category:Secrets Management ~"devops::release" ~"group::release management"
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team