Problem
When I export my config as a tar.gz then import it to it’s destination it expands in a subdirectory which is not visible to the destination site (there is also no feedback that an error has occurred, see image below). This appears to be a bug.
As you can see, thought the DSM says the configuration is ready to sync there is no config to sync! It is there, it's just one level dow in the directory structure.
The workaround is to extract the tar and then re-compress it from within the directory as a list of files (tar -cvzf config-myconfigpath.tar.gz .) then import it.
Proposed resolution
Add a step to the process of extracting the tar that removes the files from the archive directory.
Comment | File | Size | Author |
---|---|---|---|
Screen Shot 2015-12-29 at 12.13.14 PM.png | 129.48 KB | tkoleary |
Comments
Comment #2
tkoleary CreditAttribution: tkoleary at Acquia commentedComment #3
tkoleary CreditAttribution: tkoleary at Acquia commentedComment #4
tkoleary CreditAttribution: tkoleary at Acquia commentedAdded to config management usability meta #2642404: [meta] Usability improvements to configuration management post 8.0
Comment #5
xjmComment #10
quietone CreditAttribution: quietone at PreviousNext commented@tkoleary,Thank you for reporting this problem.
I tested this on 10.0.x and was not able to reproduce this error. I followed the steps given in the Issue Summary. Then I made a change to the maintenance message and re-imported the previously saved config tar. That worked as expected, reporting that 'system.maintenance' was changed.
I don't know when this was fixed so, closing as outdated. If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").
Thanks!