opensource/grafana
1
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-07-30 01:52:37 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: change URL occurences to uppercase (#22151)

Browse Source 
* change URL occurences to uppercase

* Update docs/sources/tutorials/iis.md

Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
This commit is contained in:
Jeet Parekh
2020-02-14 21:41:08 +05:30
committed by GitHub
parent 56cd845e97
commit f1989f1bfc
24 changed files with 52 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/sources/plugins/developing/auth-for-datasources.md
View File

@ -25,9 +25,9 @@ For backend authentication to work, the external/third-party API must either hav
You can specify routes in the `plugin.json` file for your data source plugin. [Here is an example](https://github.com/grafana/azure-monitor-datasource/blob/d74c82145c0a4af07a7e96cc8dde231bfd449bd9/src/plugin.json#L30-L95) with lots of routes (though most plugins will just have one route).
When you build your url to the third-party API in your data source class, the url should start with the text specified in the path field for a route. The proxy will strip out the path text and replace it with the value in the url field.
When you build your URL to the third-party API in your data source class, the URL should start with the text specified in the path field for a route. The proxy will strip out the path text and replace it with the value in the URL field.
For example, if my code makes a call to url `azuremonitor/foo/bar` with this code:
For example, if my code makes a call to URL `azuremonitor/foo/bar` with this code:
```js
this.backendSrv.datasourceRequest({

2
docs/sources/plugins/developing/plugin-review-guidelines.md
View File

@ -140,7 +140,7 @@ A basic guide for data sources can be found [here](http://docs.grafana.org/plugi
### Config Page Guidelines
- It should be as easy as possible for a user to configure a url. If the data source is using the `datasource-http-settings` component, it should use the `suggest-url` attribute to suggest the default url or a url that is similar to what it should be (especially important if the url refers to a REST endpoint that is not common knowledge for most users e.g. `https://yourserver:4000/api/custom-endpoint`).
- It should be as easy as possible for a user to configure a URL. If the data source is using the `datasource-http-settings` component, it should use the `suggest-url` attribute to suggest the default URL or a URL that is similar to what it should be (especially important if the URL refers to a REST endpoint that is not common knowledge for most users e.g. `https://yourserver:4000/api/custom-endpoint`).
```html
<datasource-http-settings