{"push_id":1382883070,"size":10,"distinct_size":2,"ref":"refs/heads/bugfix/rsyslog_clean_and_parsing","head":"2ea44712d4221861f127e30ba5d3ba8b771f416c","before":"ef308066d70be20893b65e8d99e806d87baa778b","commits":[{"sha":"7e626b9dec9ec3932526e79be950bb5586168aac","author":{"name":"Colin Saliceti","email":"c20ddd69cca5123f81b76f495aee28e803e78fe3@gmail.com"},"message":"Enable/Disable CVE notifier monitoring\n\nWe only need to monitor the application in production as it is only\ndeployed there.","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/7e626b9dec9ec3932526e79be950bb5586168aac"},{"sha":"08fdb7b2dab63094f765166076239a4ed95fba42","author":{"name":"Colin Saliceti","email":"c20ddd69cca5123f81b76f495aee28e803e78fe3@gmail.com"},"message":"CVE notifier host\n\nThe application now sends the deployment name with the host. The monitor\nmust be adjusted.","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/08fdb7b2dab63094f765166076239a4ed95fba42"},{"sha":"6402878ba2022231ebd853b7ae6ded509dadc84c","author":{"name":"Colin Saliceti","email":"c20ddd69cca5123f81b76f495aee28e803e78fe3@gmail.com"},"message":"Pass DEPLOY_ENV to CVE notifier\n\nThe application uses $DEPLOY_ENV and we need to pass it as environment\nvariable.","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/6402878ba2022231ebd853b7ae6ded509dadc84c"},{"sha":"aa2922cd619bb508f76eec079ae86093bdb408a1","author":{"name":"Alex Tomlins","email":"31b9da3a3465b3ecfa36a9fa34a21a9e359978e7@digital.cabinet-office.gov.uk"},"message":"Use latest aws-broker release from Github release.\n\nThis updates to the latest release of rds-broker. This is actually a\nno-op change because there were some changes introduced to the\nrds-broker[1] that were then reverted[2]. It's worth updating so that\nthe pipeline is up to date, making future changes easier.\n\nThis also changes the way we consume the release. We were previously\nbuilding a dev release in the pipeline from the git sources. This is\nsomewhat inefficient, and also has issues with the way that the version\nis pinned in the git resource, especially when we have to go back a\nversion. Building a release once and uploading to a git release makes\nthis much simpler, and also means that we consume the release in the\nsame way as 3rd-party releases that are published to bosh.io.\n\n[1]https://github.com/alphagov/paas-rds-broker/pull/18\n[2]https://github.com/alphagov/paas-rds-broker/pull/20","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/aa2922cd619bb508f76eec079ae86093bdb408a1"},{"sha":"3a2fd218ede057d2f3a32e12ef08c68018a889e1","author":{"name":"Hector Rivas Gandara","email":"7b7e5985d0d5e042df62f31a43aa47b3c2b7c938@gmail.com"},"message":"Perform a fly sync after login\n\nOur fly_sync_and_login.sh file will download the fly command from the\nfly server if the local file is older than the one in the server.\n\nBut if the file has been locally updated with a different version more\nrecently, for example because one environment has a different concourse\nversion, the curl command will not update the binary.\n\nBut concourse fly command provides a `fly sync` that will update the\nbinary if there is version mistmatch. We can execute this fly sync\ncommand just after login.","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/3a2fd218ede057d2f3a32e12ef08c68018a889e1"},{"sha":"0852366646bd5f87e2718e308f1b9f0e35e873b2","author":{"name":"Rafal Proszowski","email":"be32d5ede9193886444370ffeaf0b379ec923e12@digital.cabinet-office.gov.uk"},"message":"Merge pull request #580 from alphagov/update_rds_broker\n\n[#132312331] Use latest aws-broker release from Github release.","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/0852366646bd5f87e2718e308f1b9f0e35e873b2"},{"sha":"3bdea0a2ee1993522d53aa1c086aa97b8d7ff6ce","author":{"name":"Alex Tomlins","email":"31b9da3a3465b3ecfa36a9fa34a21a9e359978e7@digital.cabinet-office.gov.uk"},"message":"Merge pull request #583 from alphagov/bugfix/do_fly_sync_after_login\n\n[#support] Perform a fly sync after login","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/3bdea0a2ee1993522d53aa1c086aa97b8d7ff6ce"},{"sha":"6c37ed0d4c4ec41fd292f059fa8c1b3c4daa7ba4","author":{"name":"Alex Tomlins","email":"31b9da3a3465b3ecfa36a9fa34a21a9e359978e7@digital.cabinet-office.gov.uk"},"message":"Merge pull request #579 from alphagov/127345741_cve_notifier_improvements\n\n[#127345741] CVE notifier improvements","distinct":false,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/6c37ed0d4c4ec41fd292f059fa8c1b3c4daa7ba4"},{"sha":"f4e0cd483ffe33cb654603521b93b239e318ef9c","author":{"name":"Hector Rivas Gandara","email":"7b7e5985d0d5e042df62f31a43aa47b3c2b7c938@gmail.com"},"message":"Pass the properties to cleanup_syslog addon\n\nFrom v258 of bosh, they \"fixed\" it and now the addons in the runtime\nconfig DO NOT get the properties from the main manifest. In previous\nversions this was working but it was not expected.\n\nThe job syslog_cleanup_forwarding uses the property\nsyslog_daemon_config.enable with default true. If true, it does not do the\nclean up.\n\nThis job was added with bosh release v257, abnd we had set that value to false\nonly in the main manifest, NOT in the runtime manifest.\nAs we upgraded bosh just before merge this in #570 to v258, the behaviour\nchanged and the cleanup job did not work.\n\nIn this PR we add this config to the runtime config, allowing it to work properly.","distinct":true,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/f4e0cd483ffe33cb654603521b93b239e318ef9c"},{"sha":"2ea44712d4221861f127e30ba5d3ba8b771f416c","author":{"name":"Hector Rivas Gandara","email":"7b7e5985d0d5e042df62f31a43aa47b3c2b7c938@gmail.com"},"message":"WIP: Use syslog-forwarder with metron_agent format\n\nWIP: update the version to final version\n\nThe `metron_agent` syslog message[1]and the `syslog-release` message[2] are\nnot equivalent. Also, the syslog_release one does not include the index number\nof the VM.\n\nBeause that, when we replaced the metron_agent syslog forwarding feature\nwith the syslog-release/syslog-forwarder, the log logstash filters to\nparse the logs from logsearch-for-cloudfoundry stopped working[3]\n\nWe patched syslog-release to add the optional property\n`syslog.log_template` which will make syslog-release/syslog-forwarder\nconfigure rsyslog to send the logs using different templates, including\nthe one that metron_agent uses.\n\nIn this commit we change the release to our custom release and set the\nproperty `syslog.log_template: \"metron_agent\"` so that\nrestore our ability to parse logs.\n\n[1] https://github.com/cloudfoundry/loggregator/blob/develop/jobs/metron_agent/templates/syslog_forwarder.conf.erb#L53\n[2] https://github.com/cloudfoundry/syslog-release/blob/master/jobs/syslog_forwarder/templates/rsyslog.conf.erb#L56\n[3] https://github.com/cloudfoundry-community/logsearch-for-cloudfoundry/blob/develop/src/logsearch-config/src/logstash-filters/snippets/platform.conf#L11-L16","distinct":true,"url":"https://api.github.com/repos/alphagov/paas-cf/commits/2ea44712d4221861f127e30ba5d3ba8b771f416c"}]}
{"actor":{"display_login":"keymon"}}