Skip to content

Conversation

spuder
Copy link
Contributor

@spuder spuder commented Dec 13, 2016

The windows_package resource will download the agent over and over unless you provide a checksum.

If the checksum is missing, the behavior will continue exactly the same.
If the checksum is provided, it will prevent redownloads. Your site operators will thank you.

Note: I have not been able to test this because there appear to be problems with the vagrant box in test kitchen.

@spuder
Copy link
Contributor Author

spuder commented Dec 13, 2016

After further investigation, I'm not fully convinced that the cookbook is downloading the msi every chef run. Nevertheless its still good practice to allow users to validate files

Recipe: appdynamics::dotnet_agent
  * directory[temp] action create (up to date)
  * windows_service[MSDTC] action enable (up to date)
  * windows_service[MSDTC] action start (up to date)
  * windows_service[Winmgmt] action enable (up to date)
  * windows_service[Winmgmt] action start (up to date)
  * windows_service[COMSysApp] action enable (skipped due to only_if)
  * windows_service[COMSysApp] action start (skipped due to only_if)
  * windows_feature[IIS-RequestMonitor] action install (up to date)
  * windows_package[AppDynamics .NET Agent] action install
  Recipe: <Dynamically Defined Resource>
    * remote_file[C:\chef\cache\package\dotNetAgentSetup64-4.1.7.2.msi] action create (up to date)
     (up to date)
Recipe: appdynamics::dotnet_agent
  * template[C:\ProgramData\AppDynamics\DotNetAgent\Config\config.xml] action create (up to date)
  * windows_service[AppDynamics.Agent.Coordinator_service] action enable (up to date)
  * windows_service[AppDynamics.Agent.Coordinator_service] action start (up to date)
Starting audit phase

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant