updates to final-step-user-scripts#239
Open
ceblanton wants to merge 9 commits into
Open
Conversation
…ecurrence interval
Unneeded because users can use Cylc to trigger any particular tasks.
Alongside the existing cshell type, plugins can now declare install.method: pip with install.package and install.entry_point. Pip plugins are installed once (R1) and run with $case_yaml, $settings_yaml, and $output_dir. All data/frequency config is gated to cshell-only, fixing a KeyError for pip scripts that have no data section. Also fixes Python 3.12 SyntaxWarnings from invalid escape sequences in the cshell script template. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
Update final-step-user-script configuration to use the updated schema and support the new Data Science pip method.
Issue ticket number and link (if applicable)
Checklist before requesting a review
Manual Pipeline Run Details
Was the manual pipeline (
test_cloud_runner) triggered for this PR?Result of manual pipeline run:
(Paste relevant logs, output, or a link to the workflow run here)
How to trigger the manual pipeline:
The
test_cloud_runnerpipeline is not automatically associated as a required check with the PR; it must be triggered to test changes in a full post-processing run.To trigger the manual pipeline:
Follow the link to the
test_cloud_runneractions tab hereClick the dropdown "Run workflow":
a. If trying to merge from a branch on fre-workflows: choose branch from the first drop down, leave the next 2 inputs blank, and choose the fre-cli branch to test
b. If trying to merge from a fre-workflows fork: can skip first branch selection, input the fork name (ex: [user]/fre-workflows), input the fork's branch name, and choose the fre-cli branch to test
Click "Run workflow"
Note: you may need to reload the page to see your running workflow.