-
Notifications
You must be signed in to change notification settings - Fork 67
action: update specs #251
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
action: update specs #251
Conversation
automerge: false | ||
labels: | ||
- dependencies | ||
title: 'synchronize ecs-logging spec' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this actually working for you? 😲
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm using dry-run
in my local, let me try with my fork
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v1v#1 nop!
But by changing the target
name:
targets:
spec.json-update:
- name: Update spec.json
+ name: 'synchronize ecs-logging spec'
kind: file
sourceid: spec.json
scmid: githubConfig
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. Thanks for checking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. Thanks for checking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. Thanks for checking.
What
Use GitHub actions in addition to the
updatecli
to bump the json schemas created inecs-logging
.It runs on a daily basis and create a Pull Request if new changes exist.
Test
#250 was created with this setup
Tasks
Create PRs with the description pointing to the original change in the ecs-logging, similarly done in #235