This would mean the target is correct even if the pipeline JSON is modified such that the order of activities changes. It also makes the config more readable.
I have some code that solves this by converting the arrays returned by ConvertFrom-Json into ordered hash tables, which allow indexing via key or indexer (so existing functionality is unchanged). I'll submit a PR with the change for consideration.
We have been using the deployment config JSON file to override a timeout setting on the ADF.ProcFwk project using code like this:
It would be nicer to be able to write target property using a syntax like:
This would mean the target is correct even if the pipeline JSON is modified such that the order of activities changes. It also makes the config more readable.
I have some code that solves this by converting the arrays returned by
ConvertFrom-Json
into ordered hash tables, which allow indexing via key or indexer (so existing functionality is unchanged). I'll submit a PR with the change for consideration.