package_cloud 0.3.04 → 0.3.05

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e95f2cabf64878a9b29d2f5a2ab69436cd45ff65
-  data.tar.gz: de1217318fb28244b03147c25ae95196bd3b0781
+  metadata.gz: '092367368ac01d15e6e21b8f34017ed5d1313ccd'
+  data.tar.gz: 2b802351b14a7d73f9dec8bf1c21930d0b06d7ed
 SHA512:
-  metadata.gz: d8f05eecc8ae5cf82d7158e320e9f76c2cbcd5b70dfeda3343fdebf44dad66d25af4ac01fd7b2369202006c32a1df333cf8b80a17b69548c8f338aa266a14bc9
-  data.tar.gz: a50867145d3412871c80a5ef4683cfdebf9b9008419373efdf510f8b55dd7ffddef6dce6a7b0d02a2b5494c9756337a98be733d90739a42bba8a5696310de13c
+  metadata.gz: 2faddb5c7c061833d26a27ee13d453ecdbfed1a681debca4a6d12f0c758b28c1f5e0ceb3c1b474f6cd79bf8597e44575ed2dacdbfe0c514fd21c33784412b95e
+  data.tar.gz: 5df6f89cf42745308e8f185cd23831eb611520f9f394b33eaa86b1e331ebf6b43b1406c85348d0dcf94c2b3802f69406ddaf26c0fd59c04eeb39c660751a3861

data/README.md

@@ -11,24 +11,28 @@ Only Ruby 2.x and greater is supported, please use version 0.2.45 for Ruby 1.9 s
 
 The `package_cloud` command line client allows you to easily:
 
-* Create Node.js, Debian, RPM, RubyGem, Python, and Maven package repositories on [packagecloud](https://packagecloud.io).
-* Upload Node.js, Debian, RPM, RubyGem, Python, and Java JAR/WAR/AAR packages to your repositories.
+* Create Node.js, Debian, RPM, RubyGem, Python, and Maven package repositories
+ on [packagecloud](https://packagecloud.io).
+* Upload Node.js, Debian, RPM, RubyGem, Python, and Java JAR/WAR/AAR packages
+ to your repositories.
 * [Delete packages](https://packagecloud.io/docs#yank_pkg).
-* [Promote packages](https://packagecloud.io/docs#promote_pkg) between repositories.
+* [Promote packages](https://packagecloud.io/docs#promote_pkg) between
+ repositories.
 * Upload a package signing GPG key.
 * Create and delete [master and read
   tokens](https://packagecloud.io/docs#token_auth) to control repository
   access.
 
 This tool is intended to be used on the command line either manually or in an
-automated environment (like a build or CI process). See more examples on how to use the command-line
-interface by visiting the [CLI page](https://packagecloud.io/l/cli).
+automated environment (like a build or CI process). See more examples on how
+to use the command-line interface by visiting the
+[CLI page](https://packagecloud.io/l/cli).
 
 ## Installation
 
 Simply run:
 
-    $ gem install package_cloud
+    gem install package_cloud
 
 to install the command line client.
 
@@ -54,10 +58,11 @@ You can interact with our system programmatically as well by using our
 
 ### Creating a repository
 
-You can create a package repository named 'example' on [packagecloud](https://packagecloud.io) by running:
+You can create a package repository named 'example' on
+ [packagecloud](https://packagecloud.io) by running:
 
 ```
-$ package_cloud repository create example
+package_cloud repository create example
 ```
 
 ### Environment variables
@@ -69,6 +74,7 @@ that will override the settings found in `~/.packagecloud`:
    token (available [here](https://packagecloud.io/api_token)). If set, the
    CLI *will not* read the `~/.packagecloud` configuration file to get the API
    token.
+
 2. If and only if the `PACKAGECLOUD_TOKEN` variable is set, you may also set
    `PACKAGECLOUD_URL`. This environment should only be used by
    packagecloud:enterprise customers. It allows you to set the URL of the
@@ -84,7 +90,8 @@ repository you've created by using the `push` command.
 Most package types require specifying a `distribution/version` pair when
 uploading. See the examples that follow for more information.
 
-Please note that packages will be available for download via the packagecloud web UI
+Please note that packages will be available for download via the packagecloud
+ web UI
 immediately after they are uploaded, but they will not necessarily be
 available for installation via a package manager immediately. This is because
 our system regenerates the repository metadata needed by package managers as a
@@ -92,7 +99,8 @@ background job on our system. Jobs are added to a queue and processed.
 Processing time depends on the number of packages in your repository and the
 number of reindex jobs in front of yours.
 
-The following examples will show an example user name of `example-user` and a repository
+The following examples will show an example user name of `example-user` and a
+ repository
 name of `example-repository`.
 
 After the examples below, there will be an additional section documenting
@@ -100,10 +108,11 @@ important optional parameters you can specify when pushing packages.
 
 #### Uploading a Debian package
 
-You can upload a Debian package found at the path `/tmp/example.deb` for Ubuntu Xenial by running:
+You can upload a Debian package found at the path `/tmp/example.deb` for
+ Ubuntu Xenial by running:
 
 ```
-$ package_cloud push example-user/example-repository/ubuntu/xenial /tmp/example.deb
+package_cloud push example-user/example-repository/ubuntu/xenial /tmp/example.deb
 ```
 
 This command will upload `/tmp/example.deb` to the `example-repository`
@@ -113,7 +122,7 @@ We also support Debian source packages (DSCs). You can upload a
 `/tmp/example.dsc` for Ubuntu Xenial by running:
 
 ```
-$ package_cloud push example-user/example-repository/ubuntu/xenial /tmp/example.dsc
+package_cloud push example-user/example-repository/ubuntu/xenial /tmp/example.dsc
 ```
 
 Note that all files associated with the DSC (like source tarballs, patches,
@@ -129,7 +138,7 @@ You can upload an RPM package found at the path `/tmp/example.rpm` for CentOS
 6 by running:
 
 ```
-$ package_cloud push example-user/example-repository/el/6 /tmp/example.rpm
+package_cloud push example-user/example-repository/el/6 /tmp/example.rpm
 ```
 
 This command will upload `/tmp/example.rpm` to the `example-repository`
@@ -146,7 +155,7 @@ You can upload a RubyGem package found at the path `/tmp/example.gem` by
 running:
 
 ```
-$ package_cloud push example-user/example-repository /tmp/example.gem
+package_cloud push example-user/example-repository /tmp/example.gem
 ```
 
 This command will upload `/tmp/example.gem` to the `example-repository`
@@ -161,7 +170,7 @@ You can upload a Python package found at the path `/tmp/example.whl` by
 running:
 
 ```
-$ package_cloud push example-user/example-repository/python /tmp/example.whl
+package_cloud push example-user/example-repository/python /tmp/example.whl
 ```
 
 This command will upload `/tmp/example.whl` to the `example-repository`
@@ -174,7 +183,7 @@ eggs in PyPI repositories.
 If you'd like to upload a Python egg despite this, you can do so by running:
 
 ```
-$ package_cloud push example-user/example-repository/python /tmp/example.egg
+package_cloud push example-user/example-repository/python /tmp/example.egg
 ```
 
 #### Uploading a Java JAR, WAR, or AAR package
@@ -183,27 +192,29 @@ You can upload a Java JAR package found at the path `/tmp/example.jar` by
 running:
 
 ```
-$ package_cloud push example-user/example-repository/java/maven2 /tmp/example.jar
+package_cloud push example-user/example-repository/java/maven2 /tmp/example.jar
 ```
 
 WAR files can be uploaded the same way.
 
 It is important to note that in some cases (for example: 'fat JARs', or JARs
-without `pom.xml` files, etc) our system will not be able to automatically detect
+without `pom.xml` files, etc) our system will not be able to automatically
+ detect
 the [Maven coordinates](https://maven.apache.org/pom.html#Maven_Coordinates).
 In these cases you will receive an error, and you should specify the
 coordinates manually on the command line:
 
 ```
-$ package_cloud push example-user/example-repository/java/maven2 /tmp/example.jar --coordinates=com.mygroup:packagename:1.0.2
+package_cloud push example-user/example-repository/java/maven2 /tmp/example.jar --coordinates=com.mygroup:packagename:1.0.2
 ```
 
 #### Uploading a Node.js package
 
-To upload a Node.js package located at `/tmp/test-1.0.0.tgz` to a packagecloud NPM registry called `example-user/example-repository`:
+To upload a Node.js package located at `/tmp/test-1.0.0.tgz` to a packagecloud
+ NPM registry called `example-user/example-repository`:
 
 ```
-$ package_cloud push example-user/example-repository/node /tmp/example-1.0.tgz
+package_cloud push example-user/example-repository/node /tmp/example-1.0.tgz
 ```
 
 #### Additional options
@@ -225,7 +236,8 @@ more advanced use cases:
   continue uploading packages.
 * `--coordinates` - This flag is used for Java JARs or WARs which do not have
   an internal `pom.xml` specifying the Maven coordinates. You can specify your
-  own Maven coordinates for this file using this flag: `--coordinates=com.mygroup:packagename:1.0.2`.
+  own Maven coordinates for this file using this flag:
+   `--coordinates=com.mygroup:packagename:1.0.2`.
 * `--config` - This flag is used to specify a custom configuration file path
   for the CLI. This file specifies the website URL and your API token. This is
   default to `~/.packagecloud`.
@@ -254,7 +266,7 @@ uploaded for Ubuntu Xenial from the repository `example-repository` owned by
 the user `example-user` by running the following command:
 
 ```
-$ package_cloud yank example-user/example-repository/ubuntu/xenial example_1.0.1-1_amd64.deb
+package_cloud yank example-user/example-repository/ubuntu/xenial example_1.0.1-1_amd64.deb
 ```
 
 This will delete the package and trigger a reindex of the repository's
@@ -267,7 +279,7 @@ uploaded for CentOS 6 from the repository `example-repository` owned by
 the user `example-user` by running the following command:
 
 ```
-$ package_cloud yank example-user/example-repository/el/6 example-1.0-1.x86_64.rpm
+package_cloud yank example-user/example-repository/el/6 example-1.0-1.x86_64.rpm
 ```
 
 This will delete the package and trigger a reindex of the repository's
@@ -280,7 +292,7 @@ repository `example-repository` owned by the user `example-user`
 by running the following command:
 
 ```
-$ package_cloud yank example-user/example-repository example-1.0.gem
+package_cloud yank example-user/example-repository example-1.0.gem
 ```
 
 This will delete the package and trigger a reindex of the repository's
@@ -293,7 +305,7 @@ You can delete a Python package named `example-1.0.1.whl` from the repository
 command:
 
 ```
-$ package_cloud yank example-user/example-repository/python example-1.0.1.whl
+package_cloud yank example-user/example-repository/python example-1.0.1.whl
 ```
 
 This will delete the package and trigger a reindex of the repository's metadata.
@@ -301,12 +313,13 @@ Python eggs and sdists can be deleted in a similar manner.
 
 #### Deleting a Java package
 
-You can delete a Java package named `example-1.0.3.jar` with the group `com.groupid` from the repository
+You can delete a Java package named `example-1.0.3.jar` with the group
+ `com.groupid` from the repository
 `example-repository` owned by the user `example-user` by running the following
 command:
 
 ```
-$ package_cloud yank example-user/example-repository/java com.groupid/example-1.0.3.jar
+package_cloud yank example-user/example-repository/java com.groupid/example-1.0.3.jar
 ```
 
 This will delete the package and trigger a reindex of the repository's
@@ -319,20 +332,21 @@ You can delete a Node.js package named `example-1.0.tgz` from the NPM registry
 command:
 
 ```
-$ package_cloud yank example-user/example-repository/node example-1.0.tgz
+package_cloud yank example-user/example-repository/node example-1.0.tgz
 ```
 
 If the package has a scope, you can delete it by passing the scope like so:
 
 ```
-$ package_cloud yank example-user/example-repository/node @scoped-user/example-1.0.tgz
+package_cloud yank example-user/example-repository/node @scoped-user/example-1.0.tgz
 ```
 
 This will delete the package and trigger a reindex of the registry's
 metadata.
 
 Note that deleting Node.js packages can have unexpected side effects when
-mixed with [NPM distribution tags](https://docs.npmjs.com/getting-started/using-tags). Read
+mixed with
+ [NPM distribution tags](https://docs.npmjs.com/getting-started/using-tags). Read
 more about how [promoting on packagecloud can affect dist tags
 here.](https://packagecloud.io/docs/#node_promote)
 
@@ -358,7 +372,7 @@ your system at `/tmp/gpg.key` for the repository `example-repository` owned by
 the user `example-user`, you can run the following command:
 
 ```
-$ package_cloud gpg_key create example-user/example-repository /tmp/gpg.key
+package_cloud gpg_key create example-user/example-repository /tmp/gpg.key
 ```
 
 Note that if you attempt to upload a private key to packagecloud, we will
@@ -371,7 +385,7 @@ You can list the GPG keys associated with the repository `example-repository`
 owned by user `example-user` by running the following command:
 
 ```
-$ package_cloud gpg_key list example-user/example-repository
+package_cloud gpg_key list example-user/example-repository
 ```
 
 The key name specified in the output of this command is the key name you should
@@ -385,7 +399,7 @@ named `example-repository` and owned by the user `example-user` by running the
 following command:
 
 ```
-$ package_cloud gpg_key destroy example-user/example-repository example-user-example-repository-56D06.pub.gpg
+package_cloud gpg_key destroy example-user/example-repository example-user-example-repository-56D06.pub.gpg
 ```
 
 You can get the key name for a key you'd like to delete by using the GPG key
@@ -395,35 +409,38 @@ list command above.
 
 Package promotion is a feature which can be used to easily move packages
 between repositories. This is useful for moving a package from a private
-staging repository to a public production ready repository during a software release
-workflow.
+staging repository to a public production ready repository during a software
+ release workflow.
 
 To move a package named `example_1.0-1_amd64.deb` from the user
 `example-user`'s repository named `repo1` over to the same users repository
 named `repo2`, you would issue the following command:
 
 ```
-$ package_cloud promote example-user/repo1/ubuntu/xenial example_1.0-1_amd64.deb example-user/repo2
+package_cloud promote example-user/repo1/ubuntu/xenial example_1.0-1_amd64.deb example-user/repo2
 ```
 
-If the package has a scope (Node.js packages), you can promote it by including the scope like so:
+If the package has a scope (Node.js packages), you can promote it by including
+ the scope like so:
 
 ```
-$ package_cloud promote example-user/repo1/node @scoped-user/example-1.0.tgz example-user/repo2
+package_cloud promote example-user/repo1/node @scoped-user/example-1.0.tgz example-user/repo2
 ```
 
-If the package has a group (Java packages), you can promote it by including the group like so:
+If the package has a group (Java packages), you can promote it by
+ including the group like so:
 
 ```
-$ package_cloud promote example-user/repo1/java com.groupid/jake-2.3.jar example-user/repo2
+package_cloud promote example-user/repo1/java com.groupid/jake-2.3.jar example-user/repo2
 ```
 
-After the package is moved, a reindex will be triggered for both `repo1` and
-`repo2`.
+After the package is moved, a reindex will be triggered for both `repo1`
+ and `repo2`.
 
 Note that promoting Node.js packages can have unexpected side effects when
-mixed with [NPM distribution tags](https://docs.npmjs.com/getting-started/using-tags). Read
-more about how [promoting on packagecloud can affect dist tags
+mixed with
+[NPM distribution tags](https://docs.npmjs.com/getting-started/using-tags).
+ Read more about how [promoting on packagecloud can affect dist tags
 here](https://packagecloud.io/docs/#node_promote).
 
 ### Creating, deleting, and listing master and read tokens
@@ -451,7 +468,7 @@ you can create a master token name "Example-Token" for the repository
 command:
 
 ```
-$ package_cloud master_token create example-user/example-repository Example-Token
+package_cloud master_token create example-user/example-repository Example-Token
 ```
 
 #### Listing master tokens
@@ -461,7 +478,7 @@ You can list all master tokens associated with the repository
 command:
 
 ```
-$ package_cloud master_token list example-user/example-repository
+package_cloud master_token list example-user/example-repository
 ```
 
 #### Deleting master tokens
@@ -471,7 +488,7 @@ repository `example-repository` owned by the user `example-user` by running
 the following command:
 
 ```
-$ package_cloud master_token destroy example-user/example-repository Example-Token
+package_cloud master_token destroy example-user/example-repository Example-Token
 ```
 
 This will also automatically delete all read tokens associated with this
@@ -480,4 +497,5 @@ tokens.
 
 ## Still need help?
 
-Feel free to reach out to [support@packagecloud.io](mailto:support@packagecloud.io) with questions.
+Feel free to reach out to
+[support@packagecloud.io](mailto:support@packagecloud.io) with questions.

data/lib/package_cloud/config_file.rb

@@ -15,6 +15,10 @@ module PackageCloud
 
     def read_or_create
       if ENV["PACKAGECLOUD_TOKEN"]
+        if ENV["PACKAGECLOUD_TOKEN"].length < 48
+          puts "Found PACKAGECLOUD_TOKEN environment variable but is empty or too short! Visit https://packagecloud.io/api_token and confirm it is correct."
+          exit!
+        end
         @token = ENV["PACKAGECLOUD_TOKEN"]
         @url   = URI(ENV["PACKAGECLOUD_URL"]) if ENV["PACKAGECLOUD_URL"]
         output_host_and_token

data/lib/package_cloud/version.rb

@@ -1,7 +1,7 @@
 module PackageCloud
   MAJOR_VERSION = "0"
   MINOR_VERSION = "3"
-  PATCH_VERSION = "04"
+  PATCH_VERSION = "05"
 
   VERSION = [MAJOR_VERSION, MINOR_VERSION, PATCH_VERSION].join(".")
 end

data/markdown_lint_config.rb

@@ -0,0 +1,2 @@
+exclude_rule 'MD026'           # trailing punctuation in header
+rule 'MD029', style: "ordered" # ordered list item prefix

data/package_cloud.gemspec

@@ -27,4 +27,5 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency "bundler", "~> 1.3"
   spec.add_development_dependency "rake"
+  spec.add_development_dependency "mdl"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: package_cloud
 version: !ruby/object:Gem::Version
-  version: 0.3.04
+  version: 0.3.05
 platform: ruby
 authors:
 - Joe Damato
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-02-01 00:00:00.000000000 Z
+date: 2018-03-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
@@ -108,6 +108,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: mdl
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 description: The https://packagecloud.io CLI for uploading Node.js, Debian, RPM, RubyGem,
   Python, and Java packages. Check our website or the RubyDoc documentation for detailed
   information.
@@ -143,6 +157,7 @@ files:
 - lib/package_cloud/util.rb
 - lib/package_cloud/validator.rb
 - lib/package_cloud/version.rb
+- markdown_lint_config.rb
 - package_cloud.gemspec
 homepage: https://packagecloud.io
 licenses:
@@ -164,7 +179,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.4
+rubygems_version: 2.6.13
 signing_key: 
 specification_version: 4
 summary: The https://packagecloud.io CLI for uploading Node.js, Debian, RPM, RubyGem,