Repository navigation
fix: Support registering FAA tool using fcli tool env init command - #1127
Merged
Merged
Conversation
SangameshV
marked this pull request as draft
October 6, 2026 09:26
SangameshV
marked this pull request as ready for review
October 7, 2026 08:29
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.
This PR enhances FAA integration with FCLI by adding support for registering the Fortify Agentic Analyzer (FAA) tool through the
fcli tool env initcommand. This allows FAA to be automatically configured alongside other supported tools during environment initialization.In addition, this PR includes a couple of related fixes identified during FAA integration testing:
fortify-agentic-analyzertofortifyaato align with the current FAA binary name.NullPointerExceptionthat could occur when executing the FAA run command under specific conditions.