fix(skill): use --from/--to for openlayer export in the CLI reference - #25
Open
eastagiletracker wants to merge 1 commit into
Open
Conversation
… (v0.3.1) The Core commands table documented `openlayer export <pipelineId> <start> <end>` and the Common Mistakes table repeated that form as the fix, so an agent asked to export a date range emits it with dates. Positional start/end are the legacy Unix-timestamp-only form, so CLI 1.14.0 rejects it: $ openlayer export my-pipeline 2025-08-01 2025-08-10 Error: invalid start timestamp: strconv.ParseInt: parsing "2025-08-01": invalid syntax Document the current interface (`--from`/`--to`, plus `--last` / `--range`) and turn the mistakes row into the trap that actually bites. Patch bump across the three plugin manifests, in lockstep.
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.
This PR proposes correcting the
openlayer exporttime-range form inskills/openlayer/references/cli.md, which currently teaches an invocation the Openlayer CLI rejects. We include this PR work along with a full history of your repo at https://eastagiletracker.com/projects/289. You can sign in with your GitHub ID to claim ownership of the project.What's wrong
The Core commands table documents
openlayer exportwith the start and end times passed positionally, and the Common Mistakes table repeats that same form as the fix for gettingexportwrong. Positional start/end are the legacy arguments and parse as Unix timestamps only, so an agent that follows the reference to export a date range emits a command that never runs. Against CLI 1.14.0, installed with the script this same reference recommends:Your own command page has already moved on: https://docs.openlayer.com/api-reference/cli/commands/export.md shows every date-range example with
--from/--to, and lists the positional arguments separately as the legacy form with Unix timestamps. The reference kept the bare usage line without that distinction, so the one detail that decides whether the command runs is the one an agent does not have.The change
In
skills/openlayer/references/cli.md, the Core commands row now uses--from/--toand notes that--last 7dand--range this-weekalso work. The Common Mistakes row changes from "wrongexportarg order" to the trap that actually bites — positional times are Unix-only — and gives the working command. Nothing else in the reference changed: I re-checked the rest of its command surface against 1.14.0 (push -m/-w/-t,validate,inspect,projects create,tests -o,metrics push/run/pull/delete) and the headlessOPENLAYER_API_KEY+OPENLAYER_PROJECT_IDpath, and all of it is accurate today.Verification, replayable in a minute:
python3 scripts/validate_skills.pypasses before and after the change (frontmatter, cross-links, no orphan references, version lockstep), and the two invocations above are the before/after — the documented form fails while parsing its arguments, whileopenlayer export demo --from 2025-08-01 --to 2025-08-10parses and proceeds to the authenticated call (Invalid authentication credentials, with a dummy key). PerCONTRIBUTING.mdthis is a content fix inside the published skill, so the three manifests are bumped 0.3.0 → 0.3.1 in lockstep in the same commit; drop that hunk if you would rather bump at release time.How this was managed
This work was tracked as a single story on a board imported from this repository's own issues and pull requests (24 stories):
If you'd rather not receive contributions like this, reply
no-more-prson this pull request and we won't open any further ones on your repositories.Lawrence W. Sinclair
CEO / East Agile
linkedin.com/in/lwsinclair/
eastagile.com