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.

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

docs: explain how to mask envvars #27

Closed
wants to merge 1 commit into from

Conversation

johanneskoester
Copy link
Contributor

@johanneskoester johanneskoester commented Nov 29, 2024

fixes #22

Summary by CodeRabbit

  • Documentation
    • Updated documentation for Snakemake CLI flags to clarify local storage prefix handling for remote jobs.
    • Modified example configuration to properly escape the $JOBID variable.
    • Added a note on the importance of masking variable expansions when starting Snakemake.

Copy link

coderabbitai bot commented Nov 29, 2024

📝 Walkthrough

Walkthrough

The documentation for Snakemake CLI flags has been updated to provide clearer guidance on the use of local storage prefixes for remote jobs. Specifically, the example for the remote-job-local-storage-prefix has been modified to include an escaped variable (\$JOBID). Additionally, a new note has been added to highlight the importance of masking variable expansions when initiating Snakemake. The overall structure and content of the documentation remain unchanged, with no modifications to existing flags or their descriptions.

Changes

File Change Summary
docs/further.md Updated documentation for remote-job-local-storage-prefix to escape $JOBID and added a note on masking variable expansions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Snakemake
    participant RemoteJob

    User->>Snakemake: Start Snakemake with CLI flags
    Snakemake->>RemoteJob: Passes remote-job-local-storage-prefix
    RemoteJob->>RemoteJob: Expands \$JOBID in remote context
    RemoteJob-->>Snakemake: Executes job with local storage prefix
    Snakemake-->>User: Job execution complete
Loading

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
docs/further.md (1)

34-34: Fix grammar in the explanation

The explanation is valuable, but there's a grammatical error in the sentence.

-Here, in case a used variable can only expanded within the remote job, make sure to mask the expansion upon starting Snakemake by preceeding the variable declaration with a backslash (\$JOBID).
+Here, in case a used variable can only be expanded within the remote job, make sure to mask the expansion upon starting Snakemake by preceeding the variable declaration with a backslash (\$JOBID).
🧰 Tools
🪛 LanguageTool

[grammar] ~34-~34: Did you mean “be expanded”?
Context: ... Here, in case a used variable can only expanded within the remote job, make sure to mas...

(WILL_BASED_ON)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between fce5468 and 4ce21f9.

📒 Files selected for processing (1)
  • docs/further.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/further.md

[grammar] ~34-~34: Did you mean “be expanded”?
Context: ... Here, in case a used variable can only expanded within the remote job, make sure to mas...

(WILL_BASED_ON)

🔇 Additional comments (2)
docs/further.md (2)

26-26: LGTM! Clear example of variable escaping

The example correctly demonstrates how to escape the $JOBID variable in the configuration, which is consistent with the documentation's purpose.


26-35: Well-structured documentation enhancement

The combination of the practical example and the explanatory note effectively communicates how to handle environment variables in remote jobs. The changes are well-integrated with the existing documentation and provide clear guidance to users.

🧰 Tools
🪛 LanguageTool

[grammar] ~34-~34: Did you mean “be expanded”?
Context: ... Here, in case a used variable can only expanded within the remote job, make sure to mas...

(WILL_BASED_ON)

@johanneskoester
Copy link
Contributor Author

Closing in favor of snakemake/snakemake#3222

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.

remote-job-local-storage-prefix gets parsed in local context
1 participant