Opened 10 years ago
Closed 9 years ago
#2433 closed enhancement (fixed)
Do alias substitution for configuration documents
| Reported by: | jng | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Resource Service | Version: | |
| Severity: | trivial | Keywords: | |
| Cc: | External ID: |
Description
According to #1664, it was claimed that it was possible to create configuration documents with aliases, and they would be properly substituted.
However, according to my own tests this is not the case. Checking the resource service code confirmed my findings.
In the method MgApplicationRepositoryManager::GetResourceData(), the MgDataBindingInfo object was set to replace data file paths and user credentials, but not set to substitute aliases.
Calling dataBindingInfo.SetSubstituteUnmanagedDataMappings(true) will do the necessary substitution
Attachments (1)
Note:
See TracTickets
for help on using tickets.
I can confirm that config docs with aliases did/does work in v2.2 (create via Maestro), but no longer work in v2.6...not sure which version in between broke this. This one's a blocker for me...very much looking forward to a fix.