From 1dfeb0e45c54896d8d67a1ba9bf0b237007b728c Mon Sep 17 00:00:00 2001
From: Victor Martinez <VictorMartinezRubio@gmail.com>
Date: Tue, 4 Jun 2024 17:38:03 +0200
Subject: [PATCH] github-actions: remove snapshoty

---
 .ci/snapshoty.yml               | 33 -------------------------------
 .github/workflows/README.md     |  3 +--
 .github/workflows/snapshoty.yml | 35 ---------------------------------
 3 files changed, 1 insertion(+), 70 deletions(-)
 delete mode 100644 .ci/snapshoty.yml
 delete mode 100644 .github/workflows/snapshoty.yml

diff --git a/.ci/snapshoty.yml b/.ci/snapshoty.yml
deleted file mode 100644
index 8df340882..000000000
--- a/.ci/snapshoty.yml
+++ /dev/null
@@ -1,33 +0,0 @@
----
-
-# Version of configuration to use
-version: '1.0'
-
-# You can define a Google Cloud Account to use
-account:
-  # Project id of the service account
-  project: '${GCS_PROJECT}'
-  # Private key id of the service account
-  private_key_id: '${GCS_PRIVATE_KEY_ID}'
-  # Private key of the service account
-  private_key: '${GCS_PRIVATE_KEY}'
-  # Email of the service account
-  client_email: '${GCS_CLIENT_EMAIL}'
-  # URI token
-  token_uri: 'https://oauth2.googleapis.com/token'
-
-# List of artifacts
-artifacts:
-  # Path to use for artifacts discovery 
-  - path: './pkg'
-    # Files pattern to match
-    files_pattern: 'elastic-apm-(?P<app_version>\d+\.\d+\.\d+)\.gem'
-    # File layout on GCS bucket
-    output_pattern: '{project}/{github_branch_name}/elastic-apm-ruby-{app_version}-{github_sha_short}.gem'
-    # List of metadata processors to use.
-    metadata:
-      # Define static custom metadata
-      - name: 'custom'
-        data:
-          project: 'apm-agent-ruby'
-      - name: 'github_actions'
diff --git a/.github/workflows/README.md b/.github/workflows/README.md
index a0da49e43..eaf79fa8d 100644
--- a/.github/workflows/README.md
+++ b/.github/workflows/README.md
@@ -11,7 +11,6 @@ There are 5 main stages that run on GitHub actions:
 There are some other stages that run for every push on the main branches:
 
 * [Microbenchmark](./microbenchmark.yml)
-* [Snapshoty](./snapshoty.yml)
 
 ### Scenarios
 
@@ -50,7 +49,7 @@ The tag release follows the naming convention: `v.<major>.<minor>.<patch>`, wher
 
 ### OpenTelemetry
 
-There is a GitHub workflow in charge to populate what the workflow run in terms of jobs and steps. Those details can be seen in [here](https://ela.st/oblt-ci-cd-stats) (**NOTE**: only available for Elasticians).
+Every workflow and its logs are exported to OpenTelemetry traces/logs/metrics. Those details can be seen [here](https://ela.st/oblt-ci-cd-stats) (**NOTE**: only available for Elasticians).
 
 ## Bump automation
 
diff --git a/.github/workflows/snapshoty.yml b/.github/workflows/snapshoty.yml
deleted file mode 100644
index 19d7bc166..000000000
--- a/.github/workflows/snapshoty.yml
+++ /dev/null
@@ -1,35 +0,0 @@
-name: snapshoty
-
-on:
-  workflow_run:
-    workflows:
-      - ci
-    types:
-      - completed
-    branches:
-      - main
-
-permissions:
-  contents: read
-
-jobs:
-  publish:
-    if: ${{ github.event.workflow_run.conclusion == 'success' }}
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Download artifacts
-        run: >
-          gh run download ${{ github.event.workflow_run.id }}
-          --name package
-          --repo "${GITHUB_REPOSITORY}" 
-          --dir pkg
-        env:
-          GH_TOKEN: ${{ github.token }}
-      - name: Publish snapshot
-        uses: elastic/apm-pipeline-library/.github/actions/snapshoty-simple@current
-        with:
-          config: '.ci/snapshoty.yml'
-          vaultUrl: ${{ secrets.VAULT_ADDR }}
-          vaultRoleId: ${{ secrets.VAULT_ROLE_ID }}
-          vaultSecretId: ${{ secrets.VAULT_SECRET_ID }}