Closed (won't fix)
Project:
Variable
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Jun 2011 at 21:07 UTC
Updated:
3 Apr 2014 at 15:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
q0rban commentedRelated issue: #1201824: Variable commands step on contrib namespace
Comment #2
q0rban commentedComment #3
q0rban commentedWhoops! Accidentally added the wrong file. Keep in mind, due to #1201824 above, I had to name this file variable_api.drush.inc. :/
Comment #4
jose reyero commentedNice!
It doesn't seem to work with that file name though. Do we have any other options? Maybe adding the commands to variable_admin module instead?
Comment #5
q0rban commentedHmm, what version of drush are you using? It's working fine for me. Moving it to variable_admin may work though.
Comment #6
jose reyero commentedIt kind of works with drush 4.5, though it doesn't return anything.
With drush 5.0 I get:
(I've got drush installed with PEAR)
Comment #7
jose reyero commentedAdded Drush commands for variable realms (get, set, del)
Comment #8
bforchhammer commentedNice, this should also help with/fix #1593540: Drush command for updating domain variables.
Hm, maybe variable realms could be turned into "command options" to allow drush commands of this format:
drush variable-get site-slogan --domain=domain1 --language=enComment #9
bforchhammer commentedI had a quick go at my suggestion of turning realms into options... attached patch contains some initial work on this; I'm out of time for now, so this is only a partial patch. (Command execution does not work yet).
Comment #10
jose reyero commentedThis latter one looks more complex to me than passing realm as a parameter, or having a different function like 'variable_realm_list_all'...
Plus it seems no one is working on this anymore, feel free to reopen it anyway if you want to work on this.