hasura-allow-list-manager

KO | EN

gitlite — search

#python #ai #go #golang #android #machine-learning #rust #linux #docker #macos #awesome-list #vue #security #pytorch

hasura-allow-list-manager

(★ 10)

A manager for hasura allow list. Support for automatic addition, replacement and versioning of allow list

hasura-allow-list-manager 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Manager for hasura allow-list

Automatically Populate the Hasura allow-list from found GraphQL operations in a path, including queries, mutations, and subscriptions.
Supports update and versioning.

More on [Hasura allow-list](https://hasura.io/docs/latest/graphql/core/deployment/allow-list.html)

## Why

From hasura:
> In production instances: Enabling the allow-list is highly recommended when running the GraphQL engine in production.

Allow list is a important security feature that restrict the GraphQL engine so that it executes *only* those operations that are present in the list. But managing allow-list manually can be tendious and prone to error.

## How it works

The local queries, mutations, and subscriptions defined in `.graphql` or `.gql` files will be compared with the remote Hasura server.
The allow list manager will fetch all allowed queries from the remote Hasura instance, add new queries, update existing ones and store the final query_collection files locally. Make sure to apply the new metadata to hasura after the allow list manager ran.

### Versioning behavior

- `-v --version <version>` allows to version queries instead of updating them. This is especially useful for mobile app where client can take several weeks to update.
- The current behavior is to never remove past queries. When a query with the same name and different query is detected, it will create a new query to the allow list collection with the current timestamp and version.
- The version query name format is the following: `$NAME___($TIMESTAMP-$VERSION)`
- If you start versioning, you must continue versioning.

## Installation

```bash
npm install --save-dev @herojourneyclub/hasura-allow-list-manager
```

or yarn

```bash
yarn add --dev @herojourneyclub/hasura-allow-list-manager
```

## Usage

```bash
hasura-allow-list-manager [options]
hasura apply-metadata
```

### Options

- `-h | --host <uri>` Hasura host URI
- `-s | --admin-secret <key>` Hasura admin secret
- `-p | --path <path>` Source path with gql or graphql files
- `-f | --force-replace` Replace change queries, not prompt and asking for continue
- `-i | --allow-instrospection` Send the Introspection query with your queries
- `-r | --reset` Delete all allow lists before running insert
- `-v | --version <version>` Version queries instead of replacing them. Incompatible with -f
- `--version-max-version` Maximum number of versions to keep per query. Will always keep at least 1
- `--version-max-day` Maximum age (in days) of query versions to keep. Will always keep at least 1 
- `--query-collection-path` Path were the final query_collection will be stored

### Examples

With update:
```
hasura-allow-list-manager -h http://localhost:8080 -s my-admin-secret -p './**/*.graphql' -f
```

With versionning:
```
GIT_VERSION=$(git log --pretty=format:"%h" -1)
hasura-allow-list-manager -h http://localhost:8080 -s my-admin-secret -p './**/*.graphql' -v ${GIT_VERSION}
```

`--version-max-version` and `--version-max-age` examples:

All queries are stored in the format of `<query_name>__(<timestamp>-<version>)`. In the example the timestamp is a simple integer value.
```json
{
    "GetProfile__(1_version-1)": "query GetProfile { Users { id } }",
    "GetProfile__(2_version-2)": "query GetProfile { Users { id, firstName } }",
    "GetProfile__(3_version-3)": "query GetProfile { Users { id, lastName } }"
}
```

Running the allow list manager with `--version-max-version 2` would result in keeping the 2 most recent versions, so:

```json
{
    "GetProfile__(2_version-2)": "query GetProfile { Users { id, firstName } }",
    "GetProfile__(3_version-3)": "query GetProfile { Users { id, lastName } }"
}
```

Running the allow list manager with `--version-max-age 1` would keep all queries in the list that are 1 day old. If they are all older it would keep the most recent one.
If we assume that todays timestamp is 4 then we would keep this:

```json
{
    "GetProfile__(3_version-3)": "query GetProfile { Users { id, lastName } }"
}
```

## Development

In order to run it locally you'll need to fetch some dependencies and run the cli.

1. Install dependencies:

```bash
npm install
```

or

```bash
yarn install
```

2. To run the cli:

```
npm run dev -- -h http://localhost:8080 -s my-admin-secret -p '**/*.graphql'
```

or

```
yarn dev -h http://localhost:8080 -s my-admin-secret -p '**/*.graphql'
```

## Contributing

Contribution are welcome. Send us your PR or open a issue ticket. Let's build together.

## Credits

Fork from:
- [hasura-allowed-queries](https://github.com/TallerWebSolutions/hasura-allowed-queries)
- [hasura-allow-operations-in](https://github.com/rhyslbw/hasura-allow-operations-in) by [Rhys Bartels-Waller](https://github.com/rhyslbw)

hasura-allow-list-manager

hasura-allow-list-manager 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

hasura-allow-list-manager

hasura-allow-list-manager 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README