pingidentity-devops-getting-started
pingidentity-devops-getting-started copied to clipboard
ping-bulk-config tool add-config ignores paths with multiple slashes
Describe the bug The bulk-config-tool seems to ignore adding paths that have multiple slashes.
To Reproduce Steps to reproduce the behavior:
- get a data.json, set up env as described in docs. example of relevant section of data.json:
{
"resourceType": "/idp/spConnections",
"operationType": "SAVE",
"items": [
{}
]
},
- config.json
{
"add-config": [
{
"resourceType": "/idp/spConnections",
"item": {
"foo": "bar"
}
}
],
"config-aliases": [],
"remove-config": [],
"expose-parameters": []
}
run command:
docker run --rm -v /tmp/pftest/shared:/shared ping-bulkconfig /shared/config.json /shared/data.json /shared/env_vars /shared/data.json.subst > shared/output.log
Expected behavior output of relevant section data.json.subst should be:
{
"operationType": "SAVE",
"items": [{"foo": "bar"}],
"resourceType": "/idp/spConnections"
},
This is effectively the same as our default example in docs. working with a resource without multiple slashes (like /redirectValidation) works just fine. In fact, even just removing the second slash from "/idp/spConnections" on data.json and config.json works
@ttranatping would you mind taking a look into this?
reviving this for resolution/inquiry, @ttranatping
Hi - will look into it today/tomorrow.
I've resolved the processAddConfig issue and merged it into master @samir-gandhi @PingDavidR
Thanks @ttranatping !