Skip to content

Conversation

@manasaV3
Copy link
Contributor

@manasaV3 manasaV3 commented Dec 9, 2024

Relates to

Description

Provides ability to view the neuroglancer changes in staging before syncing it to prod.

For example, renders the neurglancer config for the run 16731 with staging resources:

python neuroglancer_util.py translate-env --run-id 16731

python neuroglancer_util.py translate-env -rn TS_026 -ds-id 10000

@manasaV3 manasaV3 marked this pull request as draft December 9, 2024 22:19
Comment on lines 35 to 39
@cli.command()
@click.argument("run_id", required=True, type=int)
@click.argument("graphql_url", required=False, type=str, default=STAGING_GRAPHQL_URL)
@click.argument("output_fileserver", required=False, type=str, default=STAGING_FILESERVER)
@click.option("--print-link", type=bool, is_flag=True, default=False)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add docs for these?

@jgadling
Copy link
Contributor

I suspect @uermel wanted a markdown file in the docs directory?

@uermel
Copy link
Contributor

uermel commented Dec 19, 2024

I'm fine with this. It may be nice to add the ability to do this via dataset id + run name, because run IDs differ between the environments. When I was reviewing this I think I accidentally tried a prod ID with the staging env, and didn't realize why it broke.

@manasaV3
Copy link
Contributor Author

@jgadling Instead of merging this, what are your thoughts on implementing the translation in the db-import as we had discussed offline?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants