-
Notifications
You must be signed in to change notification settings - Fork 106
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
feature request: pdk publish command #314
Comments
Yes, it is. I've moved it from the informal to the formal roadmap at https://tickets.puppetlabs.com/browse/PDK-579 . PS: Don't forget to like, and subscribe (that is, vote, and watch on JIRA)! |
As part of this work, is it possible to make the current "deployment" in I opened a PR on the pdk-templates but had no reply. I feel like having a |
Also related issue on pdk-templates puppetlabs/pdk-templates#51 |
Is there still plans to add a If the plan is to add a The reason I am asking is the open PR for the pdk-templates to allow customising the deploy section for TravisCI template, including removing it altogether. Either change would save us time having to remember to manually delete the section after doing a |
Yes, we do want to add publishing capabilities though there's no timeline for that right now. |
There is now a proposed RFC for a new Once accepted, that RFC can be added to the development roadmap. |
@LongLiveCHIEF @ardrigh puppetlabs-toy-chest/pdk-planning#34 has been proposed to add a |
Please review that RFC proposal if you have a moment and give your thoughts. |
It puts a real hamper in my CI/CD processes when I have to manually go upload a tarball to the forge in order to release a new update.
With a native development solution like this, is it finally time to embrace the final step of the process, and include a
pdk publish
command?The text was updated successfully, but these errors were encountered: