Closed sobjornstad closed 4 years ago
Fix merged with PR #144
Thanks!
On Tue, Jul 21, 2020, at 12:09, Giulio Vian wrote:
Fix merged with PR #144 https://github.com/tfsaggregator/aggregator-cli/pull/144
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tfsaggregator/aggregator-cli/issues/127#issuecomment-661988379, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARUZRQPBOSHL4QVORDBZGTR4XDUNANCNFSM4NMMVLZQ.
Steps to reproduce
The rule used is unlikely to be relevant, but here's a hello-world rule exhibiting the behavior, just in case:
MyTfsAggregator
.list.mappings --instance MyTfsAggregator
.Expected behavior
The mapping I just created will be listed.
Actual behavior
Suspected cause
It appears that Aggregator lowercases the name as it creates resources when installing the instance, along with appending
aggregator
, so the stored reference is tomytfsaggregatoraggregator
. When callinglist.mappings
, this lowercasing step is not carried out, causing the same input value to refer to something else.Simply referring to
mytfsaggregator
rather than theMyTfsAggregator
provided earlier in theinstall.instance
command line is sufficient to make the mappings show up.Environment
Aggregator v0.9.10, launched through Windows PowerShell 5.1. Windows 10 1809 (Build 17763.1217).