Conversation
Adds PSResource to the ProjectType enum, following the same pattern used for other FlexPack-native package managers (e.g. Choco), to support jf Install-PSResource / Publish-PSResource / Save-PSResource / Update-PSResource setup wiring. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
naveenku-jfrog
approved these changes
Sep 22, 2026
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
2 participants
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
Part of RTECO-2247 — adds
PSResourceto theProjectTypeenum, following the same pattern as every other FlexPack-native package manager, sojf setup psresourceand the PSResource FlexPack command in jfrog-cli-artifactory can reference it.Sibling PRs:
What's here
A two-line, single-file change to
common/project/projectconfig.go:PSResourceappended to theProjectTypeconst block and to theProjectTypesstring slice.Test plan
go build ./...andgo test ./common/project/...pass.gofmt/go vet/golangci-lintclean.All tests passed.
All static analysis checks passed.
Appropriate label is added to auto generate release notes.
I used gofmt for formatting the code before submitting the pull request.
PR description is clear and concise, and it includes the proposed solution/fix.
🤖 Generated with Claude Code