profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/take-five/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Alexey Mikhaylov take-five @salemove Tartu, Estonia

take-five/activerecord-hierarchical_query 99

Simple DSL for creating recursive queries with ActiveRecord

take-five/acts_as_ordered_tree 25

ActiveRecord extension for ordered adjacency trees support

salemove/ex_freddy 9

Elixir OTP behaviours for creating AMQP publishers and consumers

salemove/struct_constructor 6

An Elixir library for generating struct constructors using Ecto.Schema for handling external data

salemove/logstash_logger_formatter 3

Logstash formatter for Elixir standard Logger console backend

take-five/deferred_enum 3

Ruby Enumerable extension. Main idea is lazy computations within enumerators.

take-five/filter 3

Ruby Enumerable#filter - extended Enumerable#select combined with Enumerable#collect

salemove/tesla_statsd 1

StatsD middleware for Tesla HTTP client https://hexdocs.pm/tesla_statsd/

take-five/jstree-rails 1

A gem to automate using jsTree with Rails 3

issue commentDataDog/integrations-core

[kubernetes_state] Metrics for HPA renamed in 2.x

We fixed the issue by adding openmetrics integration onto the kube-state-metrics service:

apiVersion: v1
kind: Service
metadata:
  annotations:
    ad.datadoghq.com/service.check_names: '["kubernetes_state", "openmetrics"]'
    ad.datadoghq.com/service.init_configs: '[{}, {}]'
    # openmetrics is here to provide compatibility with KSM 2.0.0
    # See https://github.com/DataDog/integrations-core/issues/8244
    ad.datadoghq.com/service.instances: |
      [
        [
          {
            "kube_state_url": "http://%%host%%:8080/metrics",
            "prometheus_timeout": 30,
            "min_collection_interval": 30,
            "send_pod_phase_service_checks": false,
            "telemetry": true
          }
        ],
        [
          {
            "prometheus_url": "http://%%host%%:8080/metrics",
            "namespace": "kubernetes_state",
            "metrics": [
              {"kube_horizontalpodautoscaler_spec_min_replicas": "hpa.min_replicas"},
              {"kube_horizontalpodautoscaler_spec_max_replicas": "hpa.max_replicas"},
              {"kube_horizontalpodautoscaler_status_desired_replicas": "hpa.desired_replicas"},
              {"kube_horizontalpodautoscaler_status_current_replicas": "hpa.current_replicas"},
              {"kube_horizontalpodautoscaler_status_condition": "hpa.condition"},
              {"kube_node_status_capacity": "node.capacity"}
            ],
            "labels_mapper": {
              "horizontalpodautoscaler": "hpa"
            }
          }
        ]
      ]
  labels:
    app: kube-state-metrics
  name: kube-state-metrics
  namespace: kube-system
spec:
  ports:
  - name: http-metrics
    port: 8080
    targetPort: http-metrics
    protocol: TCP
  selector:
    app: kube-state-metrics
RemcodM

comment created time in 2 days

issue openedFinancial-Times/tapper_plug

What is the license of this library?

Hi, can you please add a LICENSE file? Thanks!

created time in 4 days

pull request commentsalemove/sm-docker-dd-agent

Update image for datadog agent

I'd rather we were able to check the changelog before deploying it anywhere (that's where any upgrade should start - by checking release notes).

minedetector

comment created time in 4 days

pull request commentsalemove/sm-docker-dd-agent

Update image for datadog agent

Is there release notes for this release?

minedetector

comment created time in 4 days

pull request commentsalemove/sm-docker-dd-agent

Update Datadog Agent image version

@minedetector this repository doesn't support "!plan" comments. Its pipeline is set up to build and publish a Docker image when a PR is merged to "master" branch. See https://github.com/salemove/sm-docker-dd-agent/blob/master/Jenkinsfile

minedetector

comment created time in 9 days

PullRequestReviewEvent

delete branch salemove/sm-docker-dd-agent

delete branch : renovate/datadog-agent-7.x

delete time in a month

PR closed salemove/sm-docker-dd-agent

Update datadog/agent Docker tag to v7.30.0

This PR contains the following updates:

Package Type Update Change
datadog/agent final minor 7.25.1 -> 7.30.0

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

+1 -1

0 comment

1 changed file

sm-deployer

pr closed time in a month

Pull request review commentawslabs/amazon-eks-ami

Containerd runtime support

 Environment='KUBELET_EXTRA_ARGS=$KUBELET_EXTRA_ARGS' EOF fi -# Replace with custom docker config contents.-if [[ -n "$DOCKER_CONFIG_JSON" ]]; then+if [[ "$CONTAINER_RUNTIME" = "containerd" ]]; then+    sudo mkdir -p /etc/containerd+    sudo mkdir -p /etc/cni/net.d+    sudo mv /etc/eks/containerd/containerd-config.toml /etc/containerd/config.toml+    sudo mv /etc/eks/containerd/kubelet-containerd.service /etc/systemd/system/kubelet.service+    sudo chown root:root /etc/systemd/system/kubelet.service+    systemctl daemon-reload+    systemctl enable containerd+    systemctl start containerd+elif [[ "$CONTAINER_RUNTIME" = "dockerd" ]]; then     mkdir -p /etc/docker--    echo "$DOCKER_CONFIG_JSON" > /etc/docker/daemon.json-    systemctl restart docker+    bash -c "/sbin/iptables-save > /etc/sysconfig/iptables"+    mv /etc/eks/iptables-restore.service /etc/systemd/system/iptables-restore.service+    sudo chown root:root /etc/systemd/system/iptables-restore.service+    systemctl daemon-reload+    systemctl enable iptables-restore++    if [[ -n "$DOCKER_CONFIG_JSON" ]]; then+        echo "$DOCKER_CONFIG_JSON" > /etc/docker/daemon.json+    fi+    if [[ "$ENABLE_DOCKER_BRIDGE" = "true" ]]; then+          # Enabling the docker bridge network. We have to disable live-restore as it+          # prevents docker from recreating the default bridge network on restart+          echo "$(jq '.bridge="docker0" | ."live-restore"=false' /etc/docker/daemon.json)" > /etc/docker/daemon.json+    fi+    systemctl daemon-reload+    systemctl enable docker+    systemctl start docker

Hi In the previous version of this file the Docker daemon was always restarted after its config file was modified. But after this commit nothing happens, the changes don't have an effect, probably because now the script runs systemctl start docker instead of systemctl restart docker

ravisinha0506

comment created time in 2 months

PullRequestReviewEvent

delete branch salemove/sm-docker-dd-agent

delete branch : renovate/datadog-agent-7.x

delete time in 2 months

PR closed salemove/sm-docker-dd-agent

Update datadog/agent Docker tag to v7.29.1

This PR contains the following updates:

Package Type Update Change
datadog/agent final minor 7.25.1 -> 7.29.1

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

+1 -1

0 comment

1 changed file

sm-deployer

pr closed time in 2 months

PullRequestReviewEvent
PullRequestReviewEvent

delete branch salemove/sm-docker-dd-agent

delete branch : renovate/datadog-agent-7.x

delete time in 3 months

PR closed salemove/sm-docker-dd-agent

Update datadog/agent Docker tag to v7.29.0

This PR contains the following updates:

Package Type Update Change
datadog/agent final minor 7.25.1 -> 7.29.0

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

+1 -1

0 comment

1 changed file

sm-deployer

pr closed time in 3 months

issue commenthashicorp/terraform

A way to hide certain expected changes from the "refresh" report ("Objects have changed outside of Terraform")

I think it's clear that opinions are split, and while a part of the community is happy about this change, the other part doesn't have a way to opt out.

For us it's a blocker and prevents us from upgrading to 0.15 (1.0).

petkaantonov

comment created time in 3 months

startedgo-task/task

started time in 3 months

startedchrisseaton/rhizome

started time in 3 months

startedko1nksm/getoptions

started time in 3 months

startedarkenfox/user.js

started time in 3 months

delete branch salemove/pipeline-lib

delete branch : docker-buildkit

delete time in 3 months

push eventsalemove/pipeline-lib

Alexei Mikhailov

commit sha e3bc605090c1ff5390fe5e15088d088532cd23fe

Allow using BuildKit when running `inDockerAgent` Initially, it is an "opt-in" feature as BuildKit is still considered experimental. Users can turn it on like this: ``` inDockerAgent(useBuildKit: true ```

view details

Alexey Mikhaylov

commit sha 075b094a6c2802bbf3a504561915de88d7589413

Merge pull request #115 from salemove/docker-buildkit Allow using BuildKit when running `inDockerAgent`

view details

push time in 3 months

PR merged salemove/pipeline-lib

Allow using BuildKit when running `inDockerAgent`

Initially, it is an "opt-in" feature as BuildKit is still considered experimental.

Users can turn it on like this:

inDockerAgent(useBuildKit: true)
+14 -4

0 comment

3 changed files

take-five

pr closed time in 3 months

push eventsalemove/docker-jenkins-agents

Alexei Mikhailov

commit sha c5f923d19a5e6b2a355ca41252435d52de231b5e

Enable BuildKit when building Docker agent image This will help us validate that BuildKit actually works as intended.

view details

Alexey Mikhaylov

commit sha c8d984da78ffbaaea706198ec3bae147560a56bb

Merge pull request #13 from salemove/docker-buildkit Enable BuildKit when building Docker agent image

view details

push time in 3 months

delete branch salemove/docker-jenkins-agents

delete branch : docker-buildkit

delete time in 3 months

PR merged salemove/docker-jenkins-agents

Enable BuildKit when building Docker agent image

This will help us validate that BuildKit actually works as intended.

+4 -2

1 comment

1 changed file

take-five

pr closed time in 3 months

Pull request review commentsalemove/docker-jenkins-agents

Enable BuildKit when building Docker agent image

 def buildAgentImage = { agentName, minorVersion=null -> }  withResultReporting(slackChannel: '#tm-inf') {-  inDockerAgent(containers: [agentContainer(image: 'salemove/jenkins-agent-docker:17.12.0')]) {+  inDockerAgent(containers: [agentContainer(image: 'salemove/jenkins-agent-docker:19.03.15')]) {     stage('Checkout code') {       checkout(scm)     }      stage("Build jenkins-agent-docker") {-      buildAgentImage('jenkins-agent-docker')+      withEnv(['DOCKER_BUILDKIT=1']) {

Yeah, but as far as I understand, BuildKit is smart enough to understand that there's no TTY in Jenkins and prints simple non-flashy reports.

take-five

comment created time in 3 months

PullRequestReviewEvent

PR opened salemove/pipeline-lib

Allow using BuildKit when running `inDockerAgent`

Initially, it is an "opt-in" feature as BuildKit is still considered experimental.

Users can turn it on like this:

inDockerAgent(useBuildKit: true)
+14 -4

0 comment

3 changed files

pr created time in 3 months