Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add update-specs updatcli workflow #1745

Merged
merged 3 commits into from
Feb 9, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
105 changes: 105 additions & 0 deletions .ci/update-specs.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
name: update-specs

title: synchronize schema specs

scms:
apm-agent-python:
kind: github
spec:
user: '{{ requiredEnv "GIT_USER" }}'
email: '{{ requiredEnv "GIT_EMAIL" }}'
owner: elastic
repository: apm-agent-python
token: '{{ requiredEnv "GITHUB_TOKEN" }}'
username: '{{ requiredEnv "GIT_USER" }}'
branch: main

sources:
sha:
kind: file
spec:
file: 'https://github.com/elastic/apm-data/commit/main.patch'
matchpattern: "^From\\s([0-9a-f]{40})\\s"
error.json:
kind: file
spec:
file: https://raw.githubusercontent.com/elastic/apm-data/main/input/elasticapm/docs/spec/v2/error.json
metadata.json:
kind: file
spec:
file: https://raw.githubusercontent.com/elastic/apm-data/main/input/elasticapm/docs/spec/v2/metadata.json
metricset.json:
kind: file
spec:
file: https://raw.githubusercontent.com/elastic/apm-data/main/input/elasticapm/docs/spec/v2/metricset.json
span.json:
kind: file
spec:
file: https://raw.githubusercontent.com/elastic/apm-data/main/input/elasticapm/docs/spec/v2/span.json
transaction.json:
kind: file
spec:
file: https://raw.githubusercontent.com/elastic/apm-data/main/input/elasticapm/docs/spec/v2/transaction.json
Comment on lines +23 to +42
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@axw
Is it okay for this to be a "static list" of files, or do we need something more dynamic here that considers file additions/deletions?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are our other options? The set of files won't change often, but they might still change. I think we could go ahead with this, and look at bundling the schema documents into a Compound Schema Document: http://json-schema.org/understanding-json-schema/structuring.html#bundling

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened elastic/apm-data#15 to improve this

Copy link
Member Author

@reakaleek reakaleek Feb 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another option could be a shell script that does the cloning and copying of the files. Which feels a bit hacky in the updatecli way, but is certainly possible.

Regardless, a compound schema sounds really good! This will also account for deletions.

I actually encountered a case where log.json was not removed (Also in the current implementation). (See elastic/apm-agent-nodejs#3153 (review)) A single file would fix this behaviour.

P.S.

From what I've seen, something like rsync --delete, to account for deletions, probably won't work seemlessly either.. because in some repos the schemas are in the same folder with other schemas.






actions:
pr:
kind: "github/pullrequest"
scmid: "apm-agent-python"
sourceid: sha
spec:
automerge: false
draft: false
labels:
- "automation"
description: |-
### What
APM agent json schema automatic sync
### Why
*Changeset*
* https://github.com/elastic/apm-data/commit/{{ source "sha" }}

targets:
error.json:
name: error.json
scmid: apm-agent-python
sourceid: error.json
kind: file
spec:
file: tests/upstream/json-specs/error.json
forcecreate: true
metadata.json:
name: metadata.json
scmid: apm-agent-python
sourceid: metadata.json
kind: file
spec:
file: tests/upstream/json-specs/metadata.json
forcecreate: true
metricset.json:
name: metricset.json
scmid: apm-agent-python
sourceid: metricset.json
kind: file
spec:
file: tests/upstream/json-specs/metricset.json
forcecreate: true
span.json:
name: span.json
scmid: apm-agent-python
sourceid: span.json
kind: file
spec:
file: tests/upstream/json-specs/span.json
forcecreate: true
transaction.json:
name: transaction.json
scmid: apm-agent-python
sourceid: transaction.json
kind: file
spec:
file: tests/upstream/json-specs/transaction.json
forcecreate: true
1 change: 1 addition & 0 deletions .github/workflows/opentelemetry.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ on:
- snapshoty
- release
- packages
- update-specs
types: [completed]

jobs:
Expand Down
32 changes: 32 additions & 0 deletions .github/workflows/update-specs.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
name: update-specs

on:
workflow_dispatch: ~
schedule:
- cron: '0 6 * * *'

permissions:
pull-requests: write
contents: write

jobs:
bump:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Setup Git
uses: elastic/apm-pipeline-library/.github/actions/setup-git@current
- name: Install Updatecli in the runner
uses: updatecli/updatecli-action@453502948b442d7b9a923de7b40cc7ce8628505c
- name: Run Updatecli
env:
GITHUB_TOKEN: ${{ github.token }}
BRANCH_NAME: ${{ github.ref_name }}
run: updatecli apply --config ./.ci/update-specs.yml
- if: failure()
uses: elastic/apm-pipeline-library/.github/actions/notify-build-status@current
with:
vaultUrl: ${{ secrets.VAULT_ADDR }}
vaultRoleId: ${{ secrets.VAULT_ROLE_ID }}
vaultSecretId: ${{ secrets.VAULT_SECRET_ID }}
slackChannel: "#apm-agent-python"