{"id":26059696,"url":"https://github.com/orange-cloudfoundry/cli-plugin-repo-static","last_synced_at":"2025-07-27T03:34:27.527Z","repository":{"id":78301600,"uuid":"336423539","full_name":"orange-cloudfoundry/cli-plugin-repo-static","owner":"orange-cloudfoundry","description":"cloud foundry plugin repo made static because previous repo is inactive or slow to answer","archived":false,"fork":false,"pushed_at":"2021-06-11T14:45:12.000Z","size":21819,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-08T13:29:32.845Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://orange-cloudfoundry.github.io/cli-plugin-repo-static/","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/orange-cloudfoundry.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-02-06T00:41:14.000Z","updated_at":"2021-06-11T14:44:47.000Z","dependencies_parsed_at":null,"dependency_job_id":"d8438628-5727-48e5-acd2-45651799b371","html_url":"https://github.com/orange-cloudfoundry/cli-plugin-repo-static","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/orange-cloudfoundry/cli-plugin-repo-static","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/orange-cloudfoundry%2Fcli-plugin-repo-static","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/orange-cloudfoundry%2Fcli-plugin-repo-static/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/orange-cloudfoundry%2Fcli-plugin-repo-static/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/orange-cloudfoundry%2Fcli-plugin-repo-static/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/orange-cloudfoundry","download_url":"https://codeload.github.com/orange-cloudfoundry/cli-plugin-repo-static/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/orange-cloudfoundry%2Fcli-plugin-repo-static/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":267294177,"owners_count":24065343,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-07-27T02:00:11.917Z","response_time":82,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-03-08T13:27:50.992Z","updated_at":"2025-07-27T03:34:22.513Z","avatar_url":"https://github.com/orange-cloudfoundry.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Cloud Foundry CLI Plugin Repository (CLIPR)\n\nThis is a public repository for orange and community created CF CLI plugins as a static generated website. \nIt was created to not wait approval on original repo which seems not watched anymore. \nTo submit your plugin approval, please submit a pull request according to the guidelines below.\n\nAccess to list for human: https://orange-cloudfoundry.github.io/cli-plugin-repo-static/\n\nInstall the repo on your cf cli with: `cf add-plugin-repo CF-Orange https://orange-cloudfoundry.github.io/cli-plugin-repo-static/`\n\n## Submitting Plugins\n\n1. You need to have [git](https://git-scm.com/downloads) installed\n1. Clone this repo `git clone https://github.com/cloudfoundry/cli-plugin-repo`\n1. Include your plugin information in `repo-index.yml`, here is an example of a new plugin entry\n  ```yaml\n  - authors:\n    - contact: contact@sample-author.io\n      homepage: https://github.com/sample-author\n      name: Sample-Author\n    binaries:\n    - checksum: 2a087d5cddcfb057fbda91e611c33f46\n      platform: osx\n      url: https://github.com/sample-author/new_plugin/releases/download/v1.0.0/echo_darwin\n    - checksum: b4550d6594a3358563b9dcb81e40fd66\n      platform: win64\n      url: https://github.com/sample-author/new_plugin/releases/download/v1.0.0/echo_win64.exe\n    - checksum: f6540d6594a9684563b9lfa81e23id93\n      platform: linux32\n      url: https://github.com/sample-author/new_plugin/releases/download/v1.0.0/echo_linux32\n    company:\n    created: 2015-01-31T00:00:00Z\n    description: new_plugin to be made available for the CF community\n    homepage: https://github.com/sample-author/new_plugin\n    name: new_plugin\n    updated: 2015-01-31T00:00:00Z\n    version: 1.0.0\n  ```\n  Please make sure the spacing and colons are correct and that the fields are alphabetized in the entry. The following describes each field's usage.\n\n  Field | Description\n  ------ | ---------\n  `authors` | Fields to detail the authors of the plugin\u003cbr\u003e`name`: name of author\u003cbr\u003e`homepage`: **Optional** link to the homepage of the author\u003cbr\u003e`contact`: **Optional** ways to contact author, email, twitter, phone etc ...\n  `binaries` | This section has fields detailing the various binary versions of your plugin. To reach as large an audience as possible, we encourage contributors to cross-compile their plugins on as many platforms as possible. Go provides everything you need to cross-compile for different platforms\u003cbr\u003e`platform`: The os for this binary. Supports `osx`, `linux32`, `linux64`, `win32`, `win64`\u003cbr\u003e`url`: A versioned HTTPS link to the binary file itself\u003cbr\u003e`checksum`: SHA-1 of the binary file for verification\u003cbr\u003e**Use a unique URL that includes the release version** for each release of your plugin, as each binary will have a unique checksum.\n  `company` | **Optional** field detailing company or organization that created the plugin\n  `created` | date of first submission of the plugin, in [iso 8601 combined date and time with timezone format](https://en.wikipedia.org/wiki/iso_8601#combined_date_and_time_representations)\n  `description` | describe your plugin in a line or two. this description will show up when your plugin is listed on the command line\n  `homepage` | Link to the homepage where the source code is hosted. Currently we only support open source plugins\n  `name` | name of your plugin, must not conflict with other existing plugins in the repo. **It must also match the name your plugin returns.**\n  `updated` | Date of last update of the plugin, in [ISO 8601 Combined Date and Time with Timezone Format](https://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations)\n  `version` | version number of your plugin, in [major].[minor].[build] form\n\n1. run `go run sort/main.go repo-index.yml`. This will sort your additions to the file.\n1. After making the changes, fork the repository\n1. Add your fork as a remote\n   ```\n   cd $GOPATH/src/github.com/cloudfoundry/cli-plugin-repo\n   git remote add your_name https://github.com/your_name/cli-plugin-repo\n   ```\n\n1. Push the changes to your fork and submit a Pull Request\n\n## Releasing Plugins\n\n### Cross-compile to the 3 different operating systems\n\nGolang supports cross compilation to several systems and architectures. Theres an in-depth article by Dave Cheney [here](http://dave.cheney.net/2015/08/22/cross-compilation-with-go-1-5) explaining how to do it and how it works. You can also find a list of supported systems and architectures [here](https://golang.org/doc/install/source#environment) under the `$GOOS and $GOARCH` section.\n\nThe CF cli supports 5 combinations:\n* `linux`/`386` (known as `linux32`)\n* `linux`/`amd64` (known as `linux64`)\n* `windows`/`386` (known as `win32`)\n* `windows`/`amd64` (known as `win64`)\n* `darwin `/`amd64` (known as `osx`)\n\nAnd at a minimum we want plugins to support `linux64`, `win64` and `osx`.\n\nSo, with all that, you can generate those binaries for your plugin with the following snippet:\n\n```bash\nPLUGIN_PATH=$GOPATH/src/my-plugin\nPLUGIN_NAME=$(basename $PLUGIN_PATH)\n\ncd $PLUGIN_PATH\nGOOS=linux GOARCH=amd64 go build -o ${PLUGIN_NAME}.linux64\nGOOS=linux GOARCH=386 go build -o ${PLUGIN_NAME}.linux32\nGOOS=windows GOARCH=amd64 go build -o ${PLUGIN_NAME}.win64\nGOOS=windows GOARCH=386 go build -o ${PLUGIN_NAME}.win32\nGOOS=darwin GOARCH=amd64 go build -o ${PLUGIN_NAME}.osx\n```\n\n### Sign Windows binaries\nBy signing the plugin binary, you can assure recipients that it did indeed come from you.  \nAlthough an optional step, unsigned binaries often cannot be used in locked-down machines common in organizations with stricter security policies. Signing the binary allows system admins to whitelist the plugin by signature or publisher.\n\nThe cf CLI binary is signed using a Cloud Foundry Foundation certificate. This certificate cannot be used to sign third-party plugins; plugin authors need to procure their own code-signing certificate. \n\nYou’ll need a code-signing certificate compatible with Microsoft Authenticode issued by a Microsoft-authorized certificate authority such as Thawte, Comodo, Symantec, or Digicert. *A standard code signing certificate is sufficient - extended validation (EV) is not required.* Buying direct from these CAs can be expensive. There are many resellers of certificates that pass on savings they get from volume discounts; you can shop around for a good price or support but fundamentally they’re all selling the same thing. You should expect an average price of between USD 80 and USD 150 for a one-year cert.\n\nOnce the certificate is obtained, refer to the following steps to sign your plugin binary.\n\n```bash\nCERT_LOCATION=my-cert-location\nCERT_PASSWORD=my-cert-password\nPLUGIN_BINARY_NAME=my-plugin.win32\n\nmkdir signed-binaries\nosslsigncode sign \\\n  -pkcs12 $CERT_LOCATION \\\n  -pass $CERT_PASSWORD \\\n  -t http://timestamp.comodoca.com/authenticode \\\n  -h sha256 \\\n  -in ${PLUGIN_BINARY_NAME} \\\n  -out signed-binaries/${PLUGIN_BINARY_NAME}\nrm -f ${PLUGIN_BINARY_NAME}\n```\n\n### Checksums\n\nChecksums in the `repo-index.yml` file are used to verify the integrity of the binaries, to prevent corrupted downloads from being installed. We use the [`sha-1`](https://en.wikipedia.org/wiki/SHA-1) checksum algorithm, you can compute it with: `shasum -a 1 \u003cmyfile\u003e`\n\nSo continuing the above snipped you'd do:\n\n```bash\nshasum -a 1 ${PLUGIN_NAME}.linux64\nshasum -a 1 ${PLUGIN_NAME}.linux32\nshasum -a 1 ${PLUGIN_NAME}.win64\nshasum -a 1 ${PLUGIN_NAME}.win32\nshasum -a 1 ${PLUGIN_NAME}.osx\n```\n\nTake note of those so that you can put them on `repo-index.yml` later when you have uploaded the binaries.\n\n### Release the binary publicly\n\nYou could use whatever file hosting you like here, the easiest and recommended one is GitHub releases, given that your plugin's code is already hosted on GitHub it might be the easiest solution too.\n\nYou can read more about GitHub Releases [here](https://help.github.com/articles/creating-releases/) but for the purposes of releasing your plugin you should upload those five binaries generated above on the same release.\n\nYou should then copy the resulting links for the uploaded binaries from the release page and put them on the `repo-index.yml` file.\n\nThis process can get a little tedious if you do it manually every time, that's why some plugin developers have automated it. You can probably put together scripts based on the snippets above to automate compiling, generating checksums and uploading the release to GitHub. There are tools available to manage GitHub releases such as [this one](https://github.com/aktau/github-release).\n\n\n## Running your own Plugin Repo Server\n\nIncluded as part of this repository is the CLI Plugin Repo (CLIPR), a reference implementation of a repo server. For information on how to run CLIPR or how to write your own, [please see the CLIPR documentation here.](https://github.com/cloudfoundry/cli-plugin-repo/blob/master/docs/CLIPR.md)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Forange-cloudfoundry%2Fcli-plugin-repo-static","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Forange-cloudfoundry%2Fcli-plugin-repo-static","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Forange-cloudfoundry%2Fcli-plugin-repo-static/lists"}