feat: read ESTELA_SPIDER_ARGS from environment#10
Merged
Conversation
- Read ESTELA_SPIDER_ARGS from env instead of hardcoding empty string - Fix pre-existing ruff errors (format strings, duplicate test name, noqa) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
joaquingx
force-pushed
the
feat/spider-args
branch
from
0c48a28 to
6ea344c
Compare
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.
Summary
ESTELA_SPIDER_ARGSfrom environment variable instead of hardcoding empty string""when env var is not setDetails
Previously
ESTELA_SPIDER_ARGSwas hardcoded to""insettings_remote.py. Now it reads fromos.environ, allowing the entrypoint to pass spider arguments through to the wrapper.Test plan
ESTELA_SPIDER_ARGS = ""🤖 Generated with Claude Code