Repository navigation
docs(uipath-solution): carry the traps the slimmed CLI briefing drops - #4968
vlad-uipath wants to merge 3 commits into
Conversation
|
Claude finished @vlad-uipath's task in 2m 3s —— View job SummaryThis PR adds the detail that the slimmed Change-by-Change Review1.
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | OK | Unchanged |
| E2E Tests | Issue | New capabilities have no task (see What's Missing) |
| Skill Body | Issue | SKILL.md:108 and :153 leak into the Studio Web flavor |
| References & Assets | Issue | Pointer duplication at pack-and-deploy.md:83,85; links and anchors resolve |
| Repo Hygiene | OK | Changes stay in this skill; no secrets or personal paths; no cross-skill links |
Issues for Manual Review
- Flag-level CLI claims.
assets/uip-catalog-snapshot.jsonlists verbs only, so I could confirm the verbs (solution cleanup,deploy upgrade,agent debug,maestro flow|case debug,rpa debug start,tools install) but none of the flags. These still need checking against--help:--feed-folder,--exclude-configured-sources--signing-certificate-password env.<VAR>,--signing-timestamp-server--skip-build,cleanup --skip-importsdeploy list --operation-status/--activation-status/--folder-key--governance-productand its hidden alias--automation-ops-profile
- External-app upgrade wording (
activate-and-manage.md:155) deliberately contradicts the CLI's current--help("always refused"). Please link the CLI issue once it is filed, so a later reviewer doesn't "fix" this back. - Debug commands in Studio Web. Is
uip maestro flow debug/uip rpa debug startactually exposed in the browser host? That decides what the Studio Webdebug-or-runoverride from item 1 should say.
Conclusion
Request changes (minor). The content is a clear improvement and fixes real errors. Before merge, add the two Studio Web flavor blocks (item 1) and trim the restated paragraphs in pack-and-deploy.md (item 2). Item 3 and the tests can follow later.
The CLI's scaffolded AGENTS.md shrinks to a one-line Traps list that points here, so the full detail behind each trap now lives in the skill: pack governance, dependency feeds, signing, coded-app builds, member package ids and cleanup (new pack-build-guide.md); Flow bindings, refresh warnings, failed Resource Catalog lookups, resources add/remove/edit rules, debugging vs deploying and Studio Web upload refusals (develop-solution.md); deploy list folder filters and publish 409 (pack-and-deploy.md); upgrade --config-file, feed-search failures and external-app feed upgrades (activate-and-manage.md); and matching failure-mode rows. Fixes stale statements: deploy upgrade does take --config-file; resources add --name is optional with --cloud-key and --type must match on remote; resources remove takes compound keys; deploy list folder filters run server-side; pack --name defaults to the solution folder name; packages delete needs --yes. Refs UiPath/cli#5009 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…here the tenant has the host libraries feed Matches UiPath/cli#6163: the tenant's library feeds stay in use, so the official packages resolve where the tenant includes UiPath-Official. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…aps review found - Upload 401/403: a challenge of invalid_token is worth one fresh login. Any other refusal is about grants; only an external app's 401 becomes permission_denied, a user's keeps authentication_required. A SolutionId from another tenant answers 404, not 401/403, so it is no longer named as a cause. - Publish 409: lead with publish --package-version, then re-pack. - External-app upgrade: a feed check that gets no answer is network_error / RetryLater, not a refusal. - resources remove: name the hidden-resource refusal, and say that a coded app's source/uipath_resources.ts adds a removed resource back. - Link to the governance, --exclude-configured-sources and 409 traps instead of repeating them; uppercase the deploy upgrade placeholders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
83f03ea to
be37e82
Compare
Follow-up to UiPath/cli#6237 (UiPath/cli#5009). That PR cuts the
AGENTS.mdthatuip solution initscaffolds from 121 KB to 11 KB. What's left is a one-line Traps list that points here for the detail. This PR adds that detail touipath-solutionand fixes statements the skill had wrong.Added
references/pack-build-guide.md(new, linked fromSKILL.md). It covers:Data.Projectson a failed pack--feed-folder,--nuget-sources-config-path, and why a bare--exclude-configured-sourcesusually breaks restore)solution packsolution cleanup(no prompt, and the feeds decide what it deletes)develop-solution.md:Data.ResourcesPending.flowresources add/remove/edit --patchrulesinvalid_tokenis worth one fresh login; any other is about grants. Only an external app's 401 becomespermission_denied(a user's keepsauthentication_required). ASolutionIdfrom another tenant answers 404, not 401/403resources remove: the three refusals by code (project artefact, referenced, hidden), and a coded app'ssource/uipath_resources.tsadds a removed resource back on refresh or packpack-and-deploy.md: thedeploy listfolder filters and publish 409, which leads withuip solution publish <zip> --package-version <new>(the CLI's own 409 instructions), then re-packing.activate-and-manage.md:deploy upgrade --config-file, feed-search failures, and when an external app can act on a non-tenant feed (a feed check that gets no answer isnetwork_error/RetryLater, not a refusal).failure-modes.md: 12 new rows, and the publish row now covers 409.The governance,
--exclude-configured-sourcesand publish 409 traps are stated once (pack-build guide, Version Bumping) and linked from the other places.Fixed (each checked against current
uip solution … --help):deploy upgradetakes--config-file. The skill said it takes no config file.resources add --nameis optional with--cloud-key. On remote,--typemust match the resource's type; it does more than override.resources removeaccepts compound keys, not only GUIDs.deploy list --folder-path/--folder-keyfilter on the server, soTotalcounts matches.pack --namedefault is the solution folder name (or the.uisname), not the.uipxname.packages deleteexamples were missing the required--yes.--helpstill says "always refused"; that will be raised on the CLI side.Studio Web allowlist.
tests/scripts/studioweb-browser-commands.jsongets 5allowentries with reasons, for passages that describe Node-CLI-only commands:solution packandsolution cleanupin the pack-build guidecodedapp init(prose)tools install(ResourcesPending)rpa debug startin the debugging paragraphThe alternative is Studio Web flavor overrides for those passages. Happy to switch if reviewers prefer that.
Checks
mainand the review fixes:skills:validate,skills:check-links,studioweb-browser-commands.test.mjs(20/20), and the pre-commit description check.check-sensitive-content.py --strictreports findings only in files this PR does not touch.check-skill-verbs.py: 35 findings against 34 onmain. The extra one is a false positive ontools install codedapp, the same kind as the existingtools install rpa.skills:test: two packaging tests fail the same way on unmodifiedmain.🤖 Generated with Claude Code