I am trying to deploy a folder to our IIS server. The package being deployed contains a bunch of .config files at the root level, and also contains a subfolder with its own .config files. The requirement is to have .config files in both the root level and the subfolder(s) level updated.
When I tried deploying and updating the variables, it seems only the .config in the root folder got updated, but not the one in the subfolder. Is this an Octopus limitation? The alternative I have is to package the subfolder separately and deploy it in a separate step, but I want to avoid extra work if Octopus already supports this, especially since the second package in this scenario will always have to be deployed inside the folder from the first package.
I sincerely apologize - I am no longer able to try out your suggestion because we’ve moved ahead with a workaround in this case.
I am still curious though - is this a feature supported by Octopus? And if so, is it enabled by default? If that is the case, I will see if a similar situation comes up in the future and report back if it works or not.
Thank you and I am sorry again for not being able to work with you here.
Thank you for getting back to me. I’m glad to hear you were able to implement a workaround even if we weren’t able to solve the original issue.
We do support this scenario. However, the path to the second .config file has to be passed to Octopus in the step in order to get the variables to update. We’d be happy to look at this again with you in the future when you have time.
If I can assist with anything else, please let me know
