Closed chrylis closed 10 years ago
That is what we are doing as an option. For private cloud and other CF instances (and on public cloud Redis service), we need to support a tags, labels, and uri combination.
If SC is detecting service type based on URI, why does it still filter by tag anyway instead of just always extracting credentials.uri
?
There are services such as Redis (and more on private instances of Spring Cloud) where credentials.uri field isn't set.
Ah, I'd only looked at a few of the creators, and they all just had the URIs. Looks like I can just set a custom service with credentials.uri=mongodb://user:pass@host:port/db
, correct?
Correct.
I just faceplanted into CF's inability to (AFAICT) set tags on user-provided services, meaning Spring Cloud won't pick them up. However, the MongoDB handler, at least, simply provides credentials in
credentials.uri
. Any possibility of rolling over to just inspecting those URIs instead of routing them through tag filtering?