-
Notifications
You must be signed in to change notification settings - Fork 33
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
Decodable GH actions example #23
Conversation
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.
LGTM. Is there a blog post coming on this topic, too? I vaguely remember we spoke about it at some point.
EOF | ||
|
||
- name: Apply all Decodable resources | ||
run: decodable apply $(find declarative-cicd -name '*.yaml') |
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.
Just out of curiosity: is there any specific reason for splitting up the resources into multiple files and then use find to collect them, over having everything in a single resource file?
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 can imagine in real life people may well use files and folders as ways to organise projects and resources. It'd make git diff etc a lot easier, for one thing.
Accompanying example for docs update in DE-7181.
An example of how you can integrate Decodable with your CICD workflow using GitHub Actions.