You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use wp-cli/restful with aliases where I can specify the domain using http: domain in my ~/.wp-cli/config.yml and it doesn't appear to work, like wp-cli is ignoring the http key in the configuration if it's in an alias.
Create ~/wp-cli.config.yml with just the following:
$ wp --http=wordpress.com rest status list
Error: Couldn't auto-discover WP REST API endpoint from wordpress.com.
$ wp @test-http rest status list
Warning: No WordPress install found. If the command 'rest status list' is in a plugin or theme, pass --path=`path/to/wordpress`.
Error: 'rest' is not a registered wp command. See 'wp help' for available commands.
Did you mean 'post'?
$ wp @test-ssh rest status list
Error: Cannot connect over SSH using provided configuration.
I would have expected the wp @test-http rest status list to return the same output as wp --http=wordpress.com rest status list, but instead it behaves as though http isn't set.
The text was updated successfully, but these errors were encountered:
Running wp --http=wordpress.com rest status list fails because it probably has REST API disabled. On other default installs the command (with the domain replaced) works.
This package doesn't seem to support the http parameter in the YAML file, and always requires a --http=domain.com somewhere on the command line.
I'm trying to use
wp-cli/restful
with aliases where I can specify the domain usinghttp: domain
in my~/.wp-cli/config.yml
and it doesn't appear to work, likewp-cli
is ignoring thehttp
key in the configuration if it's in an alias.Create
~/wp-cli.config.yml
with just the following:Then, try the following:
I would have expected the
wp @test-http rest status list
to return the same output aswp --http=wordpress.com rest status list
, but instead it behaves as thoughhttp
isn't set.The text was updated successfully, but these errors were encountered: