IACM workspace variables are very useful, but it can be hard to track and trace their definitions. Currently, they do not adhere to the variable organization "language" Harness has in place and established for their pipelines.
We'd like to see IACM variables as a part of that summary in Pipelines so that it's easier to trace back and see information.
Created by kinnon.yee@harness.io
·