This project provides a mechanism that allows streaming Azure logs from Azure Event Hub into Dynatrace Logs via Azure Function App. It supports both: Azure Resource Logs and Azure Activity Logs.
Introduced pipeline which runs linter, unit and integration tests on every branch. For tags starting with release it runs deployment, which creates/updates Github release with zipped code package, deployment script and deployment ARM. Paths have been updated in README. Deployment script is automatically fetching ARM template from correct release.
There are a couple 'extra' changes due additional problems which arose during pipeline creation
Pylint wasn't working with old pylint.cfg, always returning 10/10 without verifying rules. pyling.cfg has been updated to reflect current conventions in our code, some minor formatting/refactoring changes were made to fix all legible issues reported by Pylint. Test code got separate configuration, allowing more duplication and long lines, which are generally acceptable in test code
I've replaced bodyPatternMatchers in Wiremock integration test - requests which did not match were hanging indefinitely. In CI environment that is not acceptable, as we could burn through a lot of Travis credits on hanging builds (default job timeout is 1 hour)
Introduced pipeline which runs linter, unit and integration tests on every branch. For tags starting with
releaseit runs deployment, which creates/updates Github release with zipped code package, deployment script and deployment ARM. Paths have been updated in README. Deployment script is automatically fetching ARM template from correct release.You can find example test release here: https://github.com/dynatrace-oss/dynatrace-azure-log-forwarder/releases/tag/release-pipeline-test
Link to builds: https://www.travis-ci.com/github/dynatrace-oss/dynatrace-azure-log-forwarder/builds
There are a couple 'extra' changes due additional problems which arose during pipeline creation
pylint.cfg, always returning 10/10 without verifying rules.pyling.cfghas been updated to reflect current conventions in our code, some minor formatting/refactoring changes were made to fix all legible issues reported by Pylint. Test code got separate configuration, allowing more duplication and long lines, which are generally acceptable in test codebodyPatternMatchersin Wiremock integration test - requests which did not match were hanging indefinitely. In CI environment that is not acceptable, as we could burn through a lot of Travis credits on hanging builds (default job timeout is 1 hour)