Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade to Beacon 0.2 API #33

Open
mcupak opened this issue Jan 8, 2015 · 2 comments
Open

Upgrade to Beacon 0.2 API #33

mcupak opened this issue Jan 8, 2015 · 2 comments
Assignees
@mcupak
Labels
severity:major type:feature

Comments

@mcupak
Copy link
Owner

mcupak commented Jan 8, 2015

No description provided.

@mcupak mcupak self-assigned this Jan 8, 2015
@alyh
Copy link

alyh commented Apr 14, 2015

If a beacon is updated to v0.2, should we re-register it or will you rely on the BeaconInformationResource.api field to see if it upgraded?

It looks to be a required field based on this schema: https://github.com/ga4gh/schemas/blob/master/src/main/resources/avro/beacon.avdl

@mcupak
Copy link
Owner Author

mcupak commented Apr 14, 2015

In the future, we want to rely on BeaconInformationResource (for 0.2-compatible beacons). For now, beacons are registered manually. Please send us an email to [email protected] when you update your beacon.

mcupak added a commit that referenced this issue Mar 2, 2018
@mcupak
fixed #33 - added altruist beacon
132b284
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mcupak mcupak

Labels
severity:major type:feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mcupak @alyh