Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not resolve placeholder 'suite_clientid' in value "${suite_clientid}"

See original GitHub issue

When running the nighly docker image, I get the error:

Could not resolve placeholder 'suite_clientid' in value "${suite_clientid}"

Adding args.update({"suite_clientid": "foo"}) in run.py doesn’t help, and neither does args.update({"suite.oauth2.enabled": false})

Issue Analytics

State:
Created 3 years ago
Comments:11 (7 by maintainers)

Top GitHub Comments

1reaction

kolotucommented, Oct 23, 2020

I merged a change that fixed it locally, the build process in the Travis-CI pipeline is slightly different, hence I’d need to double check, whether everything works now after the build is complete. The build also updates the nightly image automatically.

1reaction

kolotucommented, Oct 23, 2020

I’ve been able to reproduce the error - I’ll look into a fix now

Top Results From Across the Web

Could not resolve placeholder in string value - java

In your configuration you have 2 PropertySourcesPlaceholderConfigurer instances. applicationContext.xml

Could not resolve placeholder 'bitbucket.home' in

Solved: I'm trying to restore Bitbucket Server to use a newly created DB. ... Could not resolve placeholder 'bitbucket.home' in value ...

java.lang.IllegalArgumentException Could not resolve ...

In this post we will see how to fix java.lang.IllegalArgumentException Could not resolve placeholder with spring boot example.

How to configure property placeholder and reference ...

IllegalArgumentException : Could not resolve placeholder 'mule.env.host' in string value "${mule.env.host}". at org.springframework.beans.factory.config.

Could not resolve placeholder 'customAuthorizationFilter ...

The project and the .war file generated on PDSOE 11.7.2 or later, fail to load on OpenEdge 11.7.0 and 11.7.1.