Repository navigation
Conversation
The palette matches a deployment's numeric id, its d<id> resource name, and a pasted pod or service name that starts with that resource name. Prompter: ACS
Preview
|
This branch was successfully deployed
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
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
The command palette (
/or the navbar search box) finds a deployment by its numeric id.Typing any of these opens that deployment:
9007199254740993)d9007199254740993)d9007199254740993-<projectId>-…)The id is indexed as hidden keywords, the same way a project's numeric id is searchable but not shown on the row. Name and location search are unchanged.
Requires deploys-app/api#142 and https://github.com/deploys-app/apiserver/pull/266 so
deployment.listreturnsidas a string-encoded int64. Until that ships, ids simply do not match; name search still works.Test plan
bun lintandbun checkbun run test tests/search.spec.jsd<id>, and a pasted pod name shows the deployment and opens its metrics pageRequested via Grok Work
Prompter: ACS