Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefix for names (teams) that might collide if exporting/importing multiple instances #32

Open
mfeferman-cx opened this issue May 12, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@mfeferman-cx
Copy link

Describe the problem

If an end-user has multiple instances of CxSAST that they would like to migrate to a single AST tenant, there is a chance for Group collisions if there are same name Teams on the source CxSAST systems.

Proposed solution

As an added command-line parameter (optional), allow the end-user to specify a prefix for exported values that may collide during Import (to the AST tenant). This initially includes Team Names (that get imported as Groups in AST), but also for any other possible colliding objects.

Additional details

None

@mfeferman-cx mfeferman-cx added the enhancement New feature or request label May 12, 2022
@duartecarneirocx
Copy link
Collaborator

Hi @mfeferman-cx,

In cxOne, Group Path is the unique field. The name is not.
So /Root/Group1 and /Root/Group2/Group1 are valid groups.
Does it solve your issue?
Do the multiple instances share the same root team name?

@mfeferman-cx
Copy link
Author

Hi @duartecarneirocx so if i have two CxSAST instances and they both have the following teams:
instance 1
\CxServer\SP\Developers

instance 2
\CxServer\SP\Developers

I'd like to be able to prepend a name to the beginning of the Team1 name, varying on a per-instance basis, so that the import would result in:

/Root/US-Developers and
/Root/India-Developers

where US == the prefix used for instance 1
and India == the prefix used for instance 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants