Elasticsearch will be used to internally search for profiles and skills registered on the platform.
More info:
Description
Description
Event Timeline
Comment Actions
The committee has decided to migrate the project to Python, and the instance has been maintained on the VPS to enable this migration. It should be deactivated in the near future (although it is currently unavailable and I don't know why).
Comment Actions
@Albertoleoncio Your tool has been granted write access to Elasticsearch now. The credentials are available to your tool as envvars. When logged into Toolforge as your tool, you can see them by running toolforge envvars list:
tools.capacity-exchange@tools-sgebastion-10:~$ toolforge envvars list name value TOOL_ELASTICSEARCH_PASSWORD redacted TOOL_ELASTICSEARCH_USER redacted TOOL_REPLICA_PASSWORD redacted TOOL_REPLICA_USER redacted TOOL_TOOLSDB_PASSWORD redacted TOOL_TOOLSDB_USER redacted
Comment Actions
@Slst2020 I'm having a problem with credentials. I don't know if I'm running it incorrectly, or if I'm missing some permission.
tools.capacity-exchange@tools-sgebastion-10:~$ toolforge envvars show TOOL_ELASTICSEARCH_PASSWORD name value TOOL_ELASTICSEARCH_PASSWORD <redacted + copied> tools.capacity-exchange@tools-sgebastion-10:~$ curl -u tools.capacity-exchange -X POST http://elasticsearch.svc.tools.eqiad1.wikimedia.cloud:80 Enter host password for user 'tools.capacity-exchange': <paste> <html><body><h1>403 Forbidden</h1> Request forbidden by administrative rules. </body></html>
Comment Actions
tools.capacity-exchange@tools-sgebastion-11:~$ toolforge envvars show TOOL_ELASTICSEARCH_PASSWORD name value TOOL_ELASTICSEARCH_PASSWORD $6$EhKG5NUX/[...]
That's a password hash, not a password...
I regenerated the credentials and copied the correct password to the envvar.