Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

Prevent fetch calls on IDL files#89

Open
peats-bond wants to merge 1 commit into
devfrom
apb/update
Open

Prevent fetch calls on IDL files#89
peats-bond wants to merge 1 commit into
devfrom
apb/update

Conversation

@peats-bond

Copy link
Copy Markdown

This change prevents users from calling idl fetch on a thrift
file. Users should be calling fetch with a service name instead.

A reported issue discovered that update wasn't fetching the latest
IDL for a service. Investigation showed that meta.json had incorrect
entries: some remotes specified a .thrift extension. This
indicates users calling idl fetch on a specifc IDL file. Reading the
meta.json file on later calls to fetch and update caused IDL to
silently fail with a 0 exit code.

Users would see IDL updates up to the first invalid entry and then IDL
would quit.

This change will update entries with .thrift extensions for
backwards compatibility.

This change prevents users from calling `idl fetch` on a thrift
file. Users should be calling `fetch` with a service name instead.

A reported issue discovered that `update` wasn't fetching the latest
IDL for a service. Investigation showed that `meta.json` had incorrect
entries: some `remotes` specified a `.thrift` extension. This
indicates users calling `idl fetch` on a specifc IDL file. Reading the
`meta.json` file on later calls to `fetch` and `update` caused IDL to
silently fail with a 0 exit code.

Users would see IDL updates up to the first invalid entry and then IDL
would quit.

This change will update entries with `.thrift` extensions for
backwards compatibility.
@peats-bond peats-bond requested a review from kriskowal May 11, 2018 21:48
@CLAassistant

CLAassistant commented May 11, 2018

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants