![]() ![]() ![]() If not, I assume that if we create permanent system vars in PS, those will be available.If a package step has PS script that sets temporary environment vars, are they accessible to scripts within Chocolatey packages that run in a subsequent step? I assume not.Using environment var may also allow us to leverage nested PDQ packages for a very efficient approach (as discussed below). ![]() These are then ready by our GfW package in order to customize the Git config files. For example, when our AWS WorkSpaces are auto-provisioned, a GPO creates a bunch of permanent system environment vars that specify the user, client, project, etc. This allows information to not only be passed at deploy-time but also at instance provisioning time. Instead, I think that using environment variables is a better way to go. While I know it is possible for PDQ Deploy to pass information via the package command line, I don’t think this is ideal. Our different Chocolatey packages have different types/levels of customization, but they all have this in common: they must be able to receive instance-specific information at deployment time that affects their operation. For example, our Chocolatey package installs Git for Windows (GfW) and then alters the Git config files so that the instance is preconfigured for a specific user. Others, however (including packages for our proprietary data migration and automated testing platforms), require significant post-install customization. ![]() Some of these packages have no customization, they are simply standard packages for installing Chrome, Java, etc. We are developing various Chocolatey deployment packages for our AWS infrastructure. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |