open-index/open-npm huggingface dataset:
npm package: @razee/clustersubscription
Description: Subscribe to razee controlled resources
Latest version: 4.0.2

# ClusterSubscription

Subscribe to Razee controlled resources

## Install

- Logon to your RazeeDash server and go to the manage org page
  - ie. `https://app.razee.io/stark-industries/org`
- Install ClusterSubscription in your cluster using the
`Install Razee Agent` command on the org page.
  - ie. `kubectl apply -f "https://app.razee.io/api/install/razeedeploy-job?orgKey=orgApiKey-..."`
- Verify that a `razee-identity` ConfigMap and Secret have been created on your cluster
- Logon to your RazeeDash server and go to the `Deployables` page to create
Cluster Groups, Channels and Subscriptions

## Environment Variables
<!--Markdownlint-disable MD034-->
<!--Markdownlint-disable MD013-->
| Name | Required | Description |
| ---- | -------- | ------------- |
| RAZEE_API           | yes | The url to your razeedash-api. ex: http://api-host:8081  Found in the `razee-identidy` ConfigMap|
| RAZEE_ORG_KEY       | yes | The orgApiKey used to communicate with razeedash-api. ex: orgApiKey-aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeer . Found in the `razee-identity` Secret|
| CLUSTER_ID          | yes | The razee defined cluster id.  Found in the `razee-identity` ConfigMap|

### Upgrading to 3.0

- If you are upgrading existing clusters to the 3.0+ release of ClusterSubscription then you will need to create
a `razee-identity` ConfigMap and Secret manually.  
  - Logon to your RazeeDash server and go to the clusters page
    - ie. `https://app.razee.io/stark-industries/clusters`
  - Click a cluster name and go to the Details tab
  - From there you will see the kubectl commands you can run to generate the `razee-identity` ConfigMap and Secret
  - Now you can add this cluster to a Cluster Group from the Deployables page
npm package: @razee/kapitan-core
Description: Core components used to extend kapitan
Latest version: 0.4.6

# kapitan-core

[![Build Status](https://travis-ci.com/razee-io/Kapitan-core.svg?branch=master)](https://travis-ci.com/razee-io/Kapitan-core)
[![Greenkeeper badge](https://badges.greenkeeper.io/razee-io/Kapitan-core.svg)](https://greenkeeper.io/)
npm package: @razee/razeedeploy-core
Description: Core components used to extend razee deploy
Latest version: 2.0.0

# razeedeploy-core

[![Build Status](https://travis-ci.com/razee-io/razeedeploy-core.svg?branch=master)](https://travis-ci.com/razee-io/razeedeploy-core)
[![Dependabot Status](https://api.dependabot.com/badges/status?host=github&repo=razee-io/razeedeploy-core)](https://dependabot.com)
![GitHub](https://img.shields.io/github/license/razee-io/RemoteResource.svg?color=success)
npm package: @razee/request-util
Description: A set of utilities to facilitate migrating from the deprecated request library to a supported library such as Axios
Author: Paul Carroll
Latest version: 1.0.11

# request-util

This module is used to make https requests with arguments supported by the `request` library
(or `request-promise-native`) but without actually using the `request` library as it is deprecated.

Instead, the **expected** arguments are converted and used with `axios`, e.g.:

- `baseUrl` --> `baseURL`
- `uri` --> `url`
- `qs` --> `params`
- etc (see `src/request.js` for full details)
- `aws` aws.key and aws.secret -> aws4.sign generated headers

Similarly, the response is modified to include attributes expected on a `request` response, e.g.:

- `data` --> `body`
- `status` --> `statusCode`
- etc (see `src/request.js` for full details)

The behavior can be compared directly to `request` behavior by uncommenting the lines prefixed
with `//COMPARE` and creating a `USE_LEGACY_REQUEST_LIBRARY` file in the base directory.
The `fs-extra`, `request`, and `request-promise-native` libraries will also need to be installed
as they are not included in `package.json`.
If this is done, `request` will be used instead of `axios`, allowing comparison.