Here is the situation and I would like to know what the expected behavior is.
I have an agent job running a package with a config file. The config file has bunch of properties set for a connection object. Let's say the connection object name is "AdventureWorks_DBConn". In the config file, there is information that says the connection object "AdventureWorks_DBConn" gets ServerName = something, Login = something, Password = something. I am posting this away from my office so I can't see the exact format of the config file, but hopefully, the experts reading this will know what I'm describing.
What happens when I edit the config file so that the connection object reference isn't "AdventureWorks_DBConn" anymore? What if I edit it to something that doesn't exist. Would you expect the agent job to:
(1) give you an error saying that you have a reference to a connection object in the config file that doesn't exist in the package? Or
(2) ignore that reference and use the values that got deployed with the package?
The behavior I am seeing is (2). But I thought I saw somewhere during my testing, that I was getting (1), but I am not able to replicate (1) and I could have been confusing myself. So I wanted to ask if someone can tell me what the expected behavior is.