Closed telday closed 3 years ago
@izgeri The GitHub action is now included in the PR, don't know how it got left out. As far as extra artifacts go, I was considering adding in the Python & Ruby generated clients because they are the most fleshed out currently. Possibly would be better to include the modified templates we used for generation instead though. let me know what you think
@telday does this match well enough with Conjur v1.11.5? please review that it's good enough before tagging.
maybe we should have the API version added to Conjur with this merge/tag, and on the next Conjur release we'll start making sure they're aligned on Conjur release
we can file an issue in cyberark/conjur to update the release workflow given the API_VERSION file in Conjur, and add the API version to the OSS status page.
@izgeri Sounds good, I will do a double check and open that issue later today before I push the tag.
Also can I have a re-approve on this? Just needed to rebase it.
What does this PR do?
Added script for collecting artifacts to be attached to each release as well as a GitHub action to release the spec on push of a version tag.
What ticket does this PR close?
Related to #111
Checklists
Change log
Test coverage
Documentation
README
s) were updated in this PR, and/or there is a follow-on issue to update docs, or