v0.2.0

ddn-assets generate command expects a new environment variable called CONN_HUB_DATA_SERVER_URL.

The assets folder looks like this now. It has two extra folders: extracts and outputs. Refer #8 for more information about them. TLDR: We will need to make use of contents of outputs for getting the connector-definition.tar.gz and the CLI plugin binaries defined as per this RFC.

.
├── downloads
│   └── hasura
│       ├── azure-cosmos
│       │   ├── v0.1.2
│       │   │   └── connector-definition.tar.gz
│       │   ├── v0.1.3
│       │   │   └── connector-definition.tar.gz
│       │   ├── v0.1.6
│       │   │   └── connector-definition.tar.gz
│       │   ├── v0.1.7
│       │   │   └── connector-definition.tar.gz
│       │   └── v0.2.0
|
├── extracts
│   └── hasura
│       ├── azure-cosmos
│       │   ├── v0.1.2
│       │   ├── v0.1.3
│       │   ├── v0.1.6
│       │   ├── v0.1.7
|
├── index.json
└── outputs
    └── hasura
        ├── azure-cosmos
        │   ├── v0.1.2
        │   │   └── connector-definition.tar.gz
        │   ├── v0.1.3
        │   │   └── connector-definition.tar.gz
        │   ├── v0.1.6
        │   │   └── connector-definition.tar.gz


553 directories, 614 files

v0.1.0

The very first version of ddn-assets 🎉

This is mainly to add support for ddn-assets generate command. This command requires NDC_HUB_GIT_REPO_FILE_PATH env var to be set as the file path to the ndc-hub repo.

The program consumes ndc-hub repo contents and emits assets of the following folder structure.

assets/
├── hasura
│   ├── azure-cosmos
│   │   ├── v0.1.2
│   │   │   └── connector-definition.tar.gz
│   │   ├── v0.1.3
│   │   │   └── connector-definition.tar.gz
│   │   ├── v0.1.6
│   │   │   └── connector-definition.tar.gz
│   │   ├── v0.1.7
│   │   │   └── connector-definition.tar.gz
│   │   └── v0.2.0
│   │       └── connector-definition.tar.gz
|
└── index.json

156 directories, 132 files