crate / croud / 727 / 2
95%
master: 95%

LAST BUILD BRANCH: h/region-header
DEFAULT BRANCH: master
Ran
Files 32
Run time 6s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 94.68%. Remained the same
727.2

Pull #264

travis-ci

web-flow 
Always use API region from config to make API calls

This commit changes the way how the `--region` argument is used for API
calls. Where previously this argument temporarily overwrote the `region`
setting from the configuration to invoke HTTP requests on the specified
region specific subdomain of `cratedb[-dev].cloud`, API requests are now
always invoked on the region specified in the configuration. However,
the HTTP request header `X-Region` is set to the value specified using
the `--region` argument, or if not present, to the value of the region
configuration setting.
This is however not the case for the `croud config set` command! This
command still sets the configuration value.

```
croud config set --region eastus2.azure --env prod

croud clusters list
\# uses the API endpoint at https://eastus2.azure.cratedb.cloud/
\# sets the X-Region header to "eastus2.azure"
\# lists all clusters of the region eastus2.azure

croud clusters list --region westeurope.azure
\# still uses the API endpoint at https://eastus2.azure.cratedb.cloud/
\# sets the X-Region header to "westeurope.azure"
\# lists all clusters of the region westeurope.azure
```

*This change requires a CrateDB Cloud version that implements the
functionality of the `X-Region` HTTP header.*
Pull Request #264: Always use API region from config to make API calls

783 of 827 relevant lines covered (94.68%)

0.95 hits per line

Source Files on job 727.2