No need to run config errand

axelaris · axelaris · commit ad237c609aee · 2018-10-30T01:11:01.000+03:00
diff --git a/deployment/operations/README.md b/deployment/operations/README.md
@@ -28,4 +28,4 @@ Includes [logsearch-for-cloudfoundry](https://github.com/cloudfoundry-community/
 
 To use this extention, you have to provide following variables: `cf_admin_password`, `uaa_admin_client_secret` and `system_domain`. You can find them in your CloudFoundry deployment variables.
 
-After deployment, please run `create-uaa-client` errand to create UAA client, and `elasticsearch_config` to upload the config. After that, you will be able to login into Logsearch UI using your CloudFoundry credentials, and use `https://logs.<YOUR_DOMAIN>` endpoint to access Logsearch UI.
+After deployment, please run `create-uaa-client` errand to create UAA client. After that, you will be able to login into Logsearch UI using your CloudFoundry credentials, and use `https://logs.<YOUR_DOMAIN>` endpoint to access Logsearch UI.

Original file line number	Diff line number	Diff line change
`@@ -28,4 +28,4 @@ Includes [logsearch-for-cloudfoundry](https://github.com/cloudfoundry-community/`
`28`	`28`
`29`	`29`	To use this extention, you have to provide following variables: `cf_admin_password`, `uaa_admin_client_secret` and `system_domain`. You can find them in your CloudFoundry deployment variables.
`30`	`30`
`31`		-After deployment, please run `create-uaa-client` errand to create UAA client, and `elasticsearch_config` to upload the config. After that, you will be able to login into Logsearch UI using your CloudFoundry credentials, and use `https://logs.<YOUR_DOMAIN>` endpoint to access Logsearch UI.
	`31`	+After deployment, please run `create-uaa-client` errand to create UAA client. After that, you will be able to login into Logsearch UI using your CloudFoundry credentials, and use `https://logs.<YOUR_DOMAIN>` endpoint to access Logsearch UI.