This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:
Current behavior:
As of #6625, TM prefers TMConfig data over CRConfig data, because the TMConfig is now generated with all the data TM needs that it used to get from the CRConfig. However, for backwards-compatibility, it will fall back on CRConfig data if the TMConfig doesn't have the new data.
New behavior:
As of this writing, the next expected ATC release is 7.0 (which should include the changes from #6625). In ATC 8.0, we should be able to remove this fallback behavior from TM so that it only ever uses data from the TMConfig. This is because the data will exist as of ATC 7.0, so in ATC 8.0 TM will no longer need to fall back to CRConfig data.
Note: we shouldn't remove the fallback behavior from TM 7.1, because that would mean TM 7.1 wouldn't work with a TO 6.1, and we generally need to support that upgrade path (latest version of the prior major version to the latest version of the current major version). Hence, why it should be removed only in ATC 8.0.
Related: #5367
Related: #1739
Related: #6512
This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:
Current behavior:
As of #6625, TM prefers TMConfig data over CRConfig data, because the TMConfig is now generated with all the data TM needs that it used to get from the CRConfig. However, for backwards-compatibility, it will fall back on CRConfig data if the TMConfig doesn't have the new data.
New behavior:
As of this writing, the next expected ATC release is 7.0 (which should include the changes from #6625). In ATC 8.0, we should be able to remove this fallback behavior from TM so that it only ever uses data from the TMConfig. This is because the data will exist as of ATC 7.0, so in ATC 8.0 TM will no longer need to fall back to CRConfig data.
Note: we shouldn't remove the fallback behavior from TM 7.1, because that would mean TM 7.1 wouldn't work with a TO 6.1, and we generally need to support that upgrade path (latest version of the prior major version to the latest version of the current major version). Hence, why it should be removed only in ATC 8.0.
Related: #5367
Related: #1739
Related: #6512