fix: database password & refactor pipelines (#99)

* chore: set pipelines by Ansible scripts

* fix: database password environment variable

* build: remove obsolete pipelines

Author: terovirtanen

azure-pipelines-notification-service-api-release.yml

@@ -26,6 +26,7 @@
     CORS_ALLOW_ALL_ORIGINS=(bool, False),
     CORS_ALLOWED_ORIGINS=(list, []),
     DATABASE_URL=(str, ""),
+    DATABASE_PASSWORD=(str, ""),
     DEBUG=(bool, False),
     DEFAULT_FROM_EMAIL=(str, "no-reply@hel.ninja"),
     HELUSERS_PASSWORD_LOGIN_DISABLED=(bool, False),
@@ -68,6 +69,9 @@
 
 DATABASES = {"default": env.db()}
 
+if env("DATABASE_PASSWORD"):
+    DATABASES["default"]["PASSWORD"] = env("DATABASE_PASSWORD")
+
 CACHES = {"default": env.cache()}
 
 try:

azure-pipelines-notification-service-api-review.yml

@@ -0,0 +1,41 @@
+# Continuous integration (CI) triggers cause a pipeline to run whenever you push
+# an update to the specified branches or you push specified tags.
+trigger:
+  batch: true
+  branches:
+    include:
+      - main
+  paths:
+    exclude:
+    - '*release-please*'
+    - '*.md'
+    - '.github/'
+    - 'pipelines/notification-service-api-release.yml'
+    - 'pipelines/notification-service-api-review.yml'
+    - '*compose*'
+
+# Pull request (PR) triggers cause a pipeline to run whenever a pull request is
+# opened with one of the specified target branches, or when updates are made to
+# such a pull request.
+#
+# GitHub creates a new ref when a pull request is created. The ref points to a
+# merge commit, which is the merged code between the source and target branches
+# of the pull request.
+#
+# Opt out of pull request validation
+pr: none
+
+# By default, use self-hosted agents
+pool: Default
+
+resources:
+  repositories:
+    # Azure DevOps repository
+    - repository: kuva-notification-service-api-pipelines
+      type: git
+      # Azure DevOps project/repository
+      name: kuva-notification-service-api/kuva-notification-service-api-pipelines
+
+extends:
+  # Filename in Azure DevOps Repository
+  template: components/notification-service-api/pipelines/notification-service-api-dev.yml@kuva-notification-service-api-pipelines

notification_service/settings.py

@@ -0,0 +1,33 @@
+# Continuous integration (CI) triggers cause a pipeline to run whenever you push
+# an update to the specified branches or you push specified tags.
+trigger:
+  batch: true
+  tags:
+    include:
+      - notification-service-api-v*
+
+# Pull request (PR) triggers cause a pipeline to run whenever a pull request is
+# opened with one of the specified target branches, or when updates are made to
+# such a pull request.
+#
+# GitHub creates a new ref when a pull request is created. The ref points to a
+# merge commit, which is the merged code between the source and target branches
+# of the pull request.
+#
+# Opt out of pull request validation
+pr: none
+
+# By default, use self-hosted agents
+pool: Default
+
+resources:
+  repositories:
+    # Azure DevOps repository
+    - repository: kuva-notification-service-api-pipelines
+      type: git
+      # Azure DevOps project/repository
+      name: kuva-notification-service-api/kuva-notification-service-api-pipelines
+
+extends:
+  # Filename in Azure DevOps Repository
+  template: components/notification-service-api/pipelines/notification-service-api-release.yml@kuva-notification-service-api-pipelines

pipelines/notification-service-api-dev.yml

@@ -1,21 +1,13 @@
 #
-# Test pipeline. Run build and deploy for Platta test environments. 
+# Review pipeline. Run build and deploy for Platta dev environments.
 # Pipeline runs different tests e.g. unittest and browser tests.
 #
-# Continuous integration (CI) triggers cause a pipeline to run whenever you push 
+# Continuous integration (CI) triggers cause a pipeline to run whenever you push
 # an update to the specified branches or you push specified tags.
-trigger:
-  batch: true
-  branches:
-    include:
-    - main
-  paths:
-    exclude:
-    - '*release-please*'
-    - '**/*.md'
-    - '.github/'
+# only PR trigger pipeline
+trigger: none
 
-# Pull request (PR) triggers cause a pipeline to run whenever a pull request is 
+# Pull request (PR) triggers cause a pipeline to run whenever a pull request is
 # opened with one of the specified target branches, or when updates are made to 
 # such a pull request.
 #
@@ -24,21 +16,31 @@ trigger:
 # of the pull request.
 #
 # Opt out of pull request validation 
-pr: none
+pr:
+  # PR target branch
+  branches:
+    include:
+    - main
+  paths:
+    exclude:
+    - '*release-please*'
+    - '*.md'
+    - '.github/'
+    - 'pipelines/notification-service-api-release.yml'
+    - 'pipelines/notification-service-api-dev.yml'
+    - '*compose*'
 
 # By default, use self-hosted agents
 pool: Default
 
 resources:
   repositories:
-  # Azure DevOps repository
-  - repository: notification-service-api-pipelines
-    type: git
-    # Azure DevOps project/repository
-    name: kuva-notification-service-api/kuva-notification-service-api-pipelines
+    # Azure DevOps repository
+    - repository: kuva-notification-service-api-pipelines
+      type: git
+      # Azure DevOps project/repository
+      name: kuva-notification-service-api/kuva-notification-service-api-pipelines
 
 extends:
-  # Filename in Azure DevOps Repository (note possible -ui or -api)
-  # Django example: azure-pipelines-PROJECTNAME-api-release.yml
-  # Drupal example: azure-pipelines-drupal-release.yml
-  template: azure-pipelines-notification-service-api-test.yml@notification-service-api-pipelines
+  # Filename in Azure DevOps Repository
+  template: components/notification-service-api/pipelines/notification-service-api-review.yml@kuva-notification-service-api-pipelines