We've hit issues in the past where old variables that have been removed from deployment cause false-positives in scripts (as they are ignored during deployment), I propose we add switches to Publish-AatAutomationPackage that will remove stale variables/modules/credentials from the automation account. I propose we create a cache variable (of sorts) that keeps track of each variable/module/credential, and which package deployed them (so as to only remove the stale variables from the current package being deployed)
We've hit issues in the past where old variables that have been removed from deployment cause false-positives in scripts (as they are ignored during deployment), I propose we add switches to Publish-AatAutomationPackage that will remove stale variables/modules/credentials from the automation account. I propose we create a cache variable (of sorts) that keeps track of each variable/module/credential, and which package deployed them (so as to only remove the stale variables from the current package being deployed)