Unpin ES and PG
We've made changes to these packages to make them work with the ldap hab
user scenario.
@@ -313,8 +313,8 @@ pins = {
# This will pin the services that we package and start with the deployment service,
# while still allowing the clients of these databases to upgrade their client
# libraries if any fixes are shipped there.
- "automate-postgresql" => {"origin" => "chef", "name" => "automate-postgresql", "version" => "9.6.11", "release" => "20200428204055"},
- "automate-elasticsearch" => {"origin" => "chef", "name" => "automate-elasticsearch", "version" => "6.8.3", "release" => "20200717180357"},
+ "automate-postgresql" => {"origin" => "chef", "name" => "automate-postgresql", "version" => "9.6.11", "release" => "20200723182209"},
+ "automate-elasticsearch" => {"origin" => "chef", "name" => "automate-elasticsearch", "version" => "6.8.3", "release" => "20200723182204"},
}
unless no_pin_hab
