Skip to content

TraGicCode/tragiccode-azure_key_vault

View on GitHub ↗Related repositories →

Pull secrets from Azure's key vault with this puppet module.

active 2024-09-102026-07-10 (UTC)

Partial coverage14,799 / 18,046 hourly files (82%) · 2 absent upstream · 3,246 failed, retryable2024-07-202026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
55
Pushes
12
Pull requests
10
Issues
3
Stars
0
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 669 days from 2024-09-10 to 2026-07-10. Pushes: 12 total, peak 6 in a day. Pull requests: 10 total, peak 5 in a day. Issues: 3 total, peak 2 in a day. Comments: 11 total, peak 4 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
TraGicCode291277
sharumpe3002
github-actions[bot]3030
yakatz1001
DennisTerrell1001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#155TraGicCode2026-02-16 16:21
    Restructure and organize README.md - Fixes #144
  • Releasegithub-actions[bot]2025-10-04 13:13
    v4.0.0
  • Pull request#153TraGicCode2025-10-04 13:12
  • Pull request#153github-actions[bot]2025-10-04 13:02
  • Pull request#152TraGicCode2025-10-04 13:02
  • Pull request#152github-actions[bot]2025-10-04 12:59
  • Pull request#151TraGicCode2025-10-04 12:42
  • Issue comment#146TraGicCode2025-03-30 02:07
    (Feature) Add ability to optionally configure a lookup hierarchy
  • Issue comment#142TraGicCode2025-03-20 04:18
    Using a key_prefix to allow for node-specific secrets
  • Issue comment#142TraGicCode2025-03-20 03:55
    Using a key_prefix to allow for node-specific secrets
  • Issue comment#142yakatz2025-03-20 02:23
    Using a key_prefix to allow for node-specific secrets
  • Issue comment#142DennisTerrell2025-03-18 23:41
    Using a key_prefix to allow for node-specific secrets
  • Releasegithub-actions[bot]2025-03-15 04:03
    v3.7.0
  • Pull request#145TraGicCode2025-03-15 04:02
  • Pull request#145github-actions[bot]2025-03-15 03:57
  • Issue#123TraGicCode2025-03-15 03:56
    multiple vaults via hierra file
  • Pull request#143TraGicCode2025-03-15 03:56
  • Issue#144TraGicCode2025-03-15 03:55
    Restructure and organize the README.md file
  • Issue comment#142sharumpe2025-03-15 01:09
    Using a key_prefix to allow for node-specific secrets
  • Pull request#143TraGicCode2025-03-15 00:54
  • Issue comment#142sharumpe2025-03-15 00:39
    Using a key_prefix to allow for node-specific secrets
  • Issue comment#123TraGicCode2025-03-15 00:29
    multiple vaults via hierra file
  • Issue comment#142TraGicCode2025-03-15 00:27
    Using a key_prefix to allow for node-specific secrets
  • Issue#142sharumpe2025-03-14 23:24
    Using a key_prefix to allow for node-specific secrets
  • Issue comment#120TraGicCode2024-09-10 21:27
    MSI on on-prem VM with azure agent

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.