Installing Prometheus and Grafana
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo add grafana https://grafana.github.io/helm-charts
helm repo update
#!/bin/bash | |
# Run the command and ignore the exit code | |
command || true | |
# Set AWS & remote backend variables | |
account="xyz" | |
account_id="123123123123" | |
bucket="bucket=${account}-tf-state" | |
backend="dynamodb_table=${account}-tf-state" |
#!/bin/bash | |
# Run the command and ignore the exit code | |
command || true | |
# Set AWS & remote backend variables | |
account="xyz" | |
account_id="123123123123" | |
bucket="bucket=${account}-tf-state" | |
backend="dynamodb_table=${account}-tf-state" |
## tf/mv-state -- Moves a given resource from one root module to another via `terraform state mv`. | |
## Example: | |
## DEST_DIR=monitor \ | |
## DEST_WORKSPACE=dev \ | |
## SRC_DIR=k8s \ | |
## SRC_WORKSPACE=dev \ | |
## RESOURCE=module.datadog_monitors \ | |
## make tf/mv-state; | |
tf/mv-state: | |
cd ./components/terraform/$(DEST_DIR); \ |
# | |
name: CI | |
on: | |
# push: | |
# branches: | |
# - 3934 | |
pull_request: | |
branches: [ develop ] |
# Copyright 2017, Google, Inc. | |
# Licensed under the Apache License, Version 2.0 (the "License") | |
FROM node:6-onbuild | |
EXPOSE 3000 | |
ENV LANGUAGE English | |
ENV API_KEY 123-456-789 |
For the first problem the first option can be by separating OWASP Dependency Check from the main pipeline and running it in a scheduled job because it adds a long extra time as it downloads and scans the historical dependency database. Along with that using CICD tool's caching mechanism depending on the tool such as Gitlab's CodeCommit's caching mechanisms.
Together with the first option can be done by separating the build step from unit tests and coverage so the team can get faster feedback and can focus on debugging the step thats causing the problem. Also, depending on the stage the project is at, unit tests can be entirely avoided if there are frequent rewrites in the code and the team needs much faster feedback. Therefore it can be implemented until the code is ready enough to face unit tests and follow test-driven dev process.
Also, security and integration test shouldn't come before unit tests as they're the most basic ones. Also its a good appraoch to run code q
{ | |
"result": "OK", | |
"data": [{ | |
"crs_id": "2426", | |
"min_price": "136,895", | |
"max_price": "156,335", | |
"img_path": "ford-kuga-8zv4o1", | |
"grp_id": "198", | |
"grp_title": "1.5 Benzin Otomatik", | |
"crs_package": "1.5 Style AT", |