When the UI is installed, the Start Tracking functionality is not working due the config directory is not created or is not writable.

CommentFileSizeAuthor
#13 1800020.13.patch4.63 KBgdrupal
#8 1800020.8.patch1.35 KBgdrupal

Comments

gdrupal’s picture

Assigned: Unassigned » gdrupal
dragonwize’s picture

We need to make sure the module will still operate in such situations though as well. It is very possible that the config files will be placed outside the doc root and made to not be writeable by the web server on purpose to be changed via deployment only. So in this case we module needs to handle this in a graceful way.

On a similar note, many IaaS (Infrastructure as a Service) hosting like Pantheon, Acquia Cloud, etc. do not allow direct access to the file system as all things get into the system via source control. Because of this we need the ability to download the entire configuration including the tracking part which is different from the migration functionality that does not need that.

gdrupal’s picture

@dragonwize so you are telling that we need to operate in a read-only mode... when if we need to move to data store will be only exporting as a tar file? but we can revert from data-store anytime... perhaps after a change trough git or whatever...

dragonwize’s picture

correct, you hit it on the head! :)

gdrupal’s picture

@dragonwize so.. cool we will cover that... on it.

dagmar’s picture

I think the current API already support all the items mentioned here.

Basically we need.

  1. A way to configure the config directory. Already implemented in 1.x, mostly copy & paste.
  2. The export UI that is being developed here: #1797114: Provide an UI to export and import configurations using Tar Files
  3. A hook_requirement that warn about the status of the config directory.
  4. Some mechanism to Start and Stop tracking without export configurations to the file system. This can be done using the export as tar feature, but maybe we can reuse the UI of the tracking and no tracking
gdrupal’s picture

about 4..
I think that @dragonwize was talking about a way to import the whole "configuration tracking stuff" for not having to deal with it manually... I was thinking to implement a configuration handler of configuration to simply import the staging table as well... only for that case... when the site is configured as "remote server' (quoting 1.x branch).

gdrupal’s picture

Status: Active » Needs review
StatusFileSize
new1.35 KB

This is a Partial patch to fix only "Config directory is not initialized" while working on all other features.

gdrupal’s picture

Status: Needs review » Needs work
neoxavier’s picture

Status: Needs work » Needs review

#8: 1800020.8.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, 1800020.8.patch, failed testing.

gdrupal’s picture

@neoxavier the partial fix patch is already commited that's why it fails.. I put the issue as "needs work" since we still are missing some other features.

gdrupal’s picture

Status: Needs work » Needs review
StatusFileSize
new4.63 KB

Work in progress.. settings form to manage configuration default path, remote server state and export tracked configuration features.

dagmar’s picture

Please add some tests if you can.

neoxavier’s picture

#13: 1800020.13.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, 1800020.13.patch, failed testing.

gdrupal’s picture

Priority: Major » Minor

This patch is already committed that why it fails.. only the test case is missing...

dagmar’s picture

Status: Needs work » Fixed

Ok I wrote the test for this feature in other issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.