I'm trying to use nbering/terraform-provider-ansible by placing it in ~/.terraform.d/plugins/linux_amd64/terraform-provider-ansible, but terraform init never seems to actually find it (NB this works fine in 0.12.x). Why is that?

Can 0.13 actually load plugins from local file-system directories (as [described in the documentation](

The ability to set the language on the user creation form could be something useful on a multi user environment.

Description
The documentation for Installing Salt for development feels like it's out of date https://docs.saltstack.com/en/latest/topics/development/hacking.html . One example is that it seems to indicate that Python2 should be used:
On Arch Linux, where Python 3 is the default installation of Python, use the virtualenv2 command instead of virtualenv.

Is your feature request related to a problem? Please describe.

AWS Fargate and ECS is a popular container cluster. Jaeger and datadog are not native to AWS, require additional setup, cost and operations. AWS X-Ray support distributed tracing for ECS and AWS lambda. A custom lambda can be developed for oauth2 token validation against Hydra. Currently tracing between lambda authorizer and hyd

Is your enhancement related to a problem? Please describe.

I often need to link to concrete che property to link it to someone. There is nice generated page in che docs with all properties https://www.eclipse.org/che/docs/che-7/installation-guide/advanced-configuration-options-for-the-che-se

I like how Simplepush presents a couple of different ways to generate push messages on their website:

https://simplepush.io/#libraries

How about having a similar feature directly in the server GUI? That would include the bits documented here https://gotify.net/docs/pushmsg