--config flag is not working as expected

[colinhuckstep]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

The --config flag appears to be ignored. The default location is always being used.

Ping CLI Version

pingcli version 0.7.0 (commit: 95cf8d3)

Affected Command(s)

• pingcli config
• pingcli request

Debug Output

pingcli config add-profile --name ci_cd --set-active --description "CI/CD" --config ./env_admin.yaml
Ping CLI configuration file 'C:\Users*/.pingcli/config.yaml' does not exist.
Creating new Ping CLI configuration file at: C:\Users*/.pingcli/config.yaml
Adding new profile 'ci_cd'...
SUCCESS: Profile created. Update additional profile attributes via 'pingcli config set' or directly within the config file at 'C:\Users**/.pingcli/config.yaml'
SUCCESS: Profile 'ci_cd' set as active.

Expected Behavior

a config file is created at the specified location and the profile is created in that config file

Actual Behavior

a config file is created in the default location and the profile is created there

Steps to Reproduce

1. pingcli config add-profile --name ci_cd --set-active --description "CI/CD" --config ./env_admin.yaml

[erikostien-pingidentity]

Hello @colinhuckstep, thank you for submitting the issue! I will take a look and provide any updates here.

[erikostien-pingidentity]

This bug issue is solved with #120, and the fix will be in the next release.