feat: appversion create with copy - av create <a>:<v> --copy-from <a>…

[gendry-gh]

feat: ssc appversion create with copy - ssc av create app:ver --copy-from app:ver2 --copy Rules,BugTracker,CustomTags,Issues

feat: copy issues from another application version - ssc av copy-issues app:ver --copy-from app:ver2

[gendry-gh]

460 : Implement new feature CopyCurrentState

109 : SSC: Add support for copying existing application version

[webmutation]

We are waiting for this feature to be available, it would save us a few steps. Any ETA when it will be released?

[alemhg]

Hello @Andhrei,

Thanks a lot for the work done to copy current state from one application to another one.

I was testing your code and after session login (ssc session login):

• when I try to create a new application version and copy the issues from another existing application version (ssc av create app:it1 --copy-from app2:it2 --copy Issues --skip-if-exists), the new application version is created but the issues (vulnerabilities) are not copied,
• when I try to copy the issues from one application version to another one (ssc av copy-issues app:ver --copy-from app2:ver) the copy fails (ACTION=COPY_FAILED).

I think it is because in the java class SSCUrls, the url defined to copy current state is set to

public static final String PROJECT_VERSIONS_ACTION_COPY_CURRENT_STATE = ApiBase + "/projectVersions/action/copyCurrentState";

Checking the request done by the browser when using FSSC, it is sent the following request:

url = "/api/v1/projectVersions/" + str(projectVersionId) + "/action" data = { "type": "COPY_CURRENT_STATE", "values": { "projectVersionId": projectVersionId, "previousProjectVersionId": previousProjectVersionId } }

I'm using Fortify SSC 23.1.2.0005.

Could you please check which URL should be used?

Best regards, Alejo

[rsenden]

We are waiting for this feature to be available, it would save us a few steps. Any ETA when it will be released?

Sorry for the delay, I'll try to review this week and create a new fcli release if all is OK. Looking at the other comment, there may still be an issue with copying current state though.

[rsenden]

Manually squash-merged after some minor code changes, rewriting commit history to generate proper changelog entries.