Feature #57161

Check for sealed config files before deploying

Added by Andreas Wolf over 7 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Won't have this time
Assignee:
-
Target version:
-
Start date:
2014-03-21
Due date:
% Done:

0%

Estimated time:

Description

When your config files are sealed, you get an error from the CopyConfiguration task, which is run very late in the deployment. This might ruin a complete deployment when you forgot to decrypt the config files, so it's probably better to check for it early in the deployment (probably in a pre-deployment check)

#1

Updated by Helmut Hummel almost 6 years ago

  • Status changed from New to Rejected
  • Priority changed from Could have to Won't have this time

I think we should provide a more generic solution for the problem which is now solved with sealed configuration

If you want to share ideas on that, feel free to add a ticket here:

https://github.com/TYPO3/Surf/issues

Also available in: Atom PDF