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

feature request: pdk publish command #314

Closed
LongLiveCHIEF opened this issue Oct 7, 2017 · 8 comments
Closed

feature request: pdk publish command #314

LongLiveCHIEF opened this issue Oct 7, 2017 · 8 comments
Labels
JIRA JIRA Ticket Created

Comments

@LongLiveCHIEF
Copy link

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?

@DavidS DavidS added the feature label Oct 9, 2017
@DavidS
Copy link
Contributor

DavidS commented Oct 9, 2017

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)!

@scotje scotje added the JIRA JIRA Ticket Created label Mar 21, 2018
@ardrigh
Copy link
Contributor

ardrigh commented Apr 4, 2018

As part of this work, is it possible to make the current "deployment" in .travisci.yml optional? Especially if the feature is looking to use puppet-blacksmith.

I opened a PR on the pdk-templates but had no reply.

I feel like having a pdk publish command would be better than including this by default in the template CI files.

@ardrigh
Copy link
Contributor

ardrigh commented Apr 12, 2018

Also related issue on pdk-templates puppetlabs/pdk-templates#51

@ardrigh
Copy link
Contributor

ardrigh commented May 8, 2018

@DavidS

Is there still plans to add a pdk publish type command? I see pdk build was added, but not yet a publish component.

If the plan is to add a publish command then these sections could drop out of the CI templates, and be replaced by a ~/.puppetforge.yml config file as per the puppet-blacksmith docs

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 pdk update 👍

@turbodog
Copy link
Contributor

turbodog commented May 8, 2018

Yes, we do want to add publishing capabilities though there's no timeline for that right now.

@scotje
Copy link
Contributor

scotje commented Jul 12, 2018

There is now a proposed RFC for a new pdk release subcommand which would include this functionality. Please add your feedback on the design to the open pull request: puppetlabs-toy-chest/pdk-planning#6

Once accepted, that RFC can be added to the development roadmap.

@scotje scotje closed this as completed Jul 12, 2018
@rodjek rodjek removed the feature label Jul 25, 2018
@scotje
Copy link
Contributor

scotje commented Jun 5, 2019

@LongLiveCHIEF @ardrigh puppetlabs-toy-chest/pdk-planning#34 has been proposed to add a pdk publish subcommand as an incremental improvement instead of waiting for all of pdk release to be implemented.

@scotje
Copy link
Contributor

scotje commented Jun 5, 2019

Please review that RFC proposal if you have a moment and give your thoughts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
JIRA JIRA Ticket Created
Projects
None yet
Development

No branches or pull requests

6 participants