Contents

require 'pdk/cli/release'

module PDK
  module CLI
    @release_publish_cmd = @release_cmd.define_command do
      name 'publish'
      usage 'publish [options] <tarball>'
      summary '(Experimental) Publishes the module <tarball> to the Forge.'

      flag nil, :force,                'Publish the module automatically, with no prompts.'

      option nil, :'forge-upload-url', 'Set forge upload url path.',
             argument: :required, default: 'https://forgeapi.puppetlabs.com/v3/releases'

      option nil, :'forge-token', 'Set Forge API token (you may also set via environment variable PDK_FORGE_TOKEN)', argument: :required

      run do |opts, _args, cmd|
        # Make sure build is being run in a valid module directory with a metadata.json
        PDK::CLI::Util.ensure_in_module!(
          message: "`pdk release #{cmd.name}` can only be run from inside a valid module with a metadata.json.",
          log_level: :info
        )

        opts[:'skip-validation'] = true
        opts[:'skip-changelog'] = true
        opts[:'skip-dependency'] = true
        opts[:'skip-documentation'] = true
        opts[:'skip-build'] = true
        opts[:'skip-versionset'] = true
        opts[:force] = true unless PDK::CLI::Util.interactive?
        opts[:'forge-token'] ||= PDK::Util::Env['PDK_FORGE_TOKEN']

        if opts[:'forge-token'].nil? || opts[:'forge-token'].empty?
          PDK.logger.error 'You must supply a Forge API token either via `--forge-token` option or PDK_FORGE_TOKEN environment variable.'
          exit 1
        end

        Release.prepare_publish_interview(TTY::Prompt.new(help_color: :cyan), opts) unless opts[:force]

        release = PDK::Module::Release.new(nil, opts)

        release.run
      end
    end
  end
end

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
pdk-3.4.0	lib/pdk/cli/release/publish.rb
pdk-3.3.0	lib/pdk/cli/release/publish.rb