Skip to content

fix: prevent assigning incorrect resource ID for sensitive variables with same name, type and at least one matching scope #539

fix: prevent assigning incorrect resource ID for sensitive variables with same name, type and at least one matching scope

fix: prevent assigning incorrect resource ID for sensitive variables with same name, type and at least one matching scope #539