Skip to content
New issue

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

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

Already on GitHub? # to your account

eNATL feedstock #8

Merged
merged 1 commit into from
Jul 12, 2024
Merged

eNATL feedstock #8

merged 1 commit into from
Jul 12, 2024

Conversation

norlandrhagen
Copy link
Contributor

A pruned version of this recipe is running locally for me.

cc @SammyAgrawal

If this seems good, we should give it a go on dataflow. 🚀
image

Copy link
Contributor

@SammyAgrawal SammyAgrawal left a comment

Choose a reason for hiding this comment

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

Allowing copy_to_local since dataset small; will continue trying to fix

@jbusecke
Copy link
Contributor

jbusecke commented Jul 9, 2024

@norlandrhagen @SammyAgrawal should we run this on dataflow?

@SammyAgrawal
Copy link
Contributor

I think we can/ should. I would like to be walked through that process

@jbusecke
Copy link
Contributor

Ill outline my steps here:

  1. I navigate to "Actions" and choose "Deploy Recipe...
image
  1. Notice that I cannot run the action from a fork branch 🤦‍♂️

jbusecke added a commit to leap-stc/LEAP_template_feedstock that referenced this pull request Jul 12, 2024
Since we had some trouble in leap-stc/eNATL_feedstock#8 I added a warning.
@jbusecke
Copy link
Contributor

Ok I have added a warning about not working from forks in leap-stc/LEAP_template_feedstock#49.

To move on here, I will merge this PR and then call the workflow from main.

@jbusecke jbusecke merged commit 97b8b78 into leap-stc:main Jul 12, 2024
1 check passed
@jbusecke
Copy link
Contributor

@SammyAgrawal The steps I am taking now are outlined here!

@jbusecke
Copy link
Contributor

jbusecke commented Jul 12, 2024

Ok so far I ran into the following issues (please see #9 for more explanations):

  • The secret to auth to gcloud was not set. This has to happen on the leap-stc org level!
  • We have some restrictions on naming for the jobs, which are in turn made up from the recipe id. This deployment failed due to the presence of an underscore.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants