- π«π·France frondeau Nantes, FRANCE
I know that this question is old now but I think we could answer to it: how do we use
drush dcem
with node nids ? I can remember we can hoose the content we want to generate by the id.
Would love to see this helpful text in the documentation be added to the drush helpful text:
default_content:
node:
- c9a89616-7057-4971-8337-555e425ed782
- b6d6d9fd-4f28-4918-b100-ffcfb15c9374
I suspect, you use UUID versus NID because it can be any entity and this is the easiest way to load it regardless of what entity type is passed in the info file? How would I best get the UUID for a node? I originally started with the use case of I only need to move < 5 nodes to other environments and was using drush dce
to implement this. Now I see my use case growing to 15-20 and think it would be great to leverage drush dcem
. However, it doesn't seem to be an easy task to track down UUID. I now have exported yml, so I can just copy and paste the UUID into the module's info file but wondering if I am missing something basic.
Another possibility, we could create a drush command that takes the results of content/node parsing it for UUIDs and appends it to the info file? This will allow developers to quickly port over to dcem when they hit a critical mass of nodes.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I know that this question is old now but I think we could answer to it: how do we use drush dcem
with node nids ? I can remember we can hoose the content we want to generate by the id.