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

Define the end-point over which we serve data product schemas #895

Closed
mferrera opened this issue Dec 6, 2024 · 0 comments · Fixed by #957
Closed

Define the end-point over which we serve data product schemas #895

mferrera opened this issue Dec 6, 2024 · 0 comments · Fixed by #957
Assignees
@mferrera
Labels
milestone Relevant to the current milestone

Comments

@mferrera
Copy link
Collaborator

mferrera commented Dec 6, 2024

The Radix instance will also come to serve schemas for products that we can provide a schema for -- typically products that can be transmitted as structured ASCII files.

We need to decide on a generic location for these files and also change the Radix app deploy script(s) + configuration for them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mferrera mferrera

Labels
milestone Relevant to the current milestone
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ENH: Produce inplace volumes result schema mferrera/fmu-dataio
1 participant
@mferrera