Graphman - goid issue

[Rajesh Natarajan]

My source & target goids for identity provider is different. Due to that when i import bundle to target I am seeing provider not found error. I tried to use revise command. it didn't help. Any suggestion how to fix this. this happen only when we promote new bundle. with existing bundle with diff command it's mapping automatically

graphman revise --input C:\Temp\graphmanworkspace\qa\delta.json --output C:\Temp\graphmanworkspace\qa\revised-delta.json --options.normalize true --options.excludeGoids 

[Raju Gurram]

Currently, graphman-diff command helps to identify goid-level differences between source and target environments and ensures to adjust the delta policies with the target environment goids. 

When it does, you will observe the below line from the console output

[info]   revising <some-policy-or-service>, replacing <source-goid> with <target-goid>

Please note that, if you have already mutated the target environment with wrong goids, please remove them (either by deleting the fragment or deleting the faulty assertion). So that, differences will be noticeable.

[Rajesh Natarajan]

Yes as mentioned i my original message, if promote a policy which is exist in target, I am able to see

[info]   revising graphmantest_fragment_3-[graphmantest_fragment_3-FRAGMENT], replacing a585deb033bfe2bffc9de914f1cb6bad with 05b478e330dc37bdb6810ceaa96d525d
[info]   revising graphmantest_fragment-[graphmantest_fragment-FRAGMENT], replacing a585deb033bfe2bffc9de914f1cb6bad with 05b478e330dc37bdb6810ceaa96d525d

If I promote a policy which is not exists in target, goid is not getting revised

C:\Users\rn3d>graphman diff --input-source C:\Temp\graphmanworkspace\qa\graphman-export_qa.json --input-target C:\Temp\graphmanworkspace\qa\graphman-export_uat.json --output C:\Temp\graphmanworkspace\qa\delta.json --output-report C:\Temp\graphmanworkspace\qa\delta-report.json
[warn] failed to load the multiline-text-diff extension, cause=MODULE_NOT_FOUND, falling back to the default
[info] inspecting clusterProperties
[info]   selecting fcb.testgraphman, category=inserts
[info] inspecting ldapIdps
[info]   selecting FCPD, category=inserts
[info] inspecting policies
[info]   selecting graphmantest_fragment-[graphmantest_fragment-FRAGMENT], category=inserts
[info]   selecting graphmantest_fragment_1-[graphmantest_fragment_1-FRAGMENT], category=inserts
[info]   selecting graphmantest_fragment_3-[graphmantest_fragment_3-FRAGMENT], category=inserts
[info] inspecting secrets
[info]   selecting testgraphman, category=inserts
[info] inspecting services
[info]   selecting testgraphman-[/testgraphman*-WEB_API], category=inserts
[warn] unknown entities, properties
[warn] unknown entities, properties
[info] writing to file C:\Temp\graphmanworkspace\qa\delta-report.json
[info] writing to file C:\Temp\graphmanworkspace\qa\delta.json

C:\Users\rn3d>

If you see the attached file the target doesn't have any policy. In this case it's not updating the goid

Attachment(s)

graphman-export_uat.json   328 B 1 version