I have a project that deploys a dacpac using the community step template “SQL - Deploy DACPAC from Package Parameter”. I am aware that this does not reference the package in the usual way and that package details are not available from octopus variables as a result. To get round this I added a “Run a script” step at the start of my deployment process with the package referenced and ticked the box “the package will not be acquired” this informs me:
“The package will not be downloaded. Package metadata variables will be still be available (e.g. Octopus.Action.Package.PackageId)”
I can see from the release manager that the package is referenced and when I add the package variables to the script in that step I can reference it with the following:
However when i copy the template from here,into an email step, no packages show up in the resulting email. It doesn’t even get into the if block so it’s just not registering that the step has a package associated with it. Is this expected behaviour?