xendren

Yes. It just has one line to specify the company truststore with our self-signed CA cert chain: `org.gradle.jvmargs=-Djavax.net.ssl.trustStore="../../../../modules/Common/security/cacerts" -Djavax.net.ssl.trustStorePassword=`

I don't have IntelliJ installed, but it looks like it is the same issue. This seems more of an issue with how extensions execute in the IDE's rather than a...

If I run the gradle task for the same project outside of VS Code, it works fine with the relative path.

Also, relative paths work in other contexts. It seems that having JVM parameters in the gradle.properties file gets added earlier than once the gradle build prepares to execute. Although not...

Our developer has figured out a work around for the time being. He is using the "Task Explorer" extension to surface some custom added tasks in the project's tasks.json file....

Apologies for jumping in here, but I have the same issue trying to deploy a component in kubernetes. We have installed dapr to our k8s cluster using the helm chart...

> > Apologies for jumping in here, but I have the same issue trying to deploy a component in kubernetes. We have installed dapr to our k8s cluster using the...

> Hi @xendren, thanks for opening the issue. Yes, it is currently by design. You'll need separate deployments of the operator to support different teams at once. > > This...

Hey... yes. We run it on the command line now and pass the options for the type of load test using the --config parameter. This is critical to being able...

For anyone else looking for the answer, this did work. If we load the options.json file in the runner image, we can provide the options at runtime. Hopefully, this will...