The process hangs when a 204 No Content error occurs while running pingcli platform export. #169

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

Ping CLI Version

pingcli version 0.8.3 (commit: f64b1f6)

Affected Command(s)

pingcli platform export --output-directory . --overwrite

Debug Output

$ env | rg PING_LOG_LEVEL && ./pingcli platform export --output-directory . --overwrite
PING_LOG_LEVEL=DEBUG
Exporting pingone-authorize service...
Exporting pingone-mfa service...
Exporting pingone-platform service...
API Function Name: ReadRecaptchaConfiguration
Resource Type: pingone_forms_recaptcha_v2
Response Code: 204 No Content
Response Body: {}
WARNING: API client 204 No Content response.

Panic Output

don't panic

Expected Behavior

pingcli should terminate successfully.

After displaying "WARNING: API client 204 No Content response.", the application hangs and the command does not exit.

Actual Behavior

Steps to Reproduce

pingcli config set service.pingOne.authentication.type=client_credentials
pingcli config set service.pingOne.authentication.clientCredentials.clientID=<CLIENT_ID>
pingcli config set service.pingOne.authentication.clientCredentials.clientSecret=<CLIENT_SECRET>
pingcli config set service.pingOne.authentication.environmentID=<ENVIRONMENT_ID>
pingcli config set service.pingOne.regionCode=AP    # 必要に応じてリージョンを指定する
pingcli config set export.pingOne.environmentID=<ENVIRONMENT_ID>
pingcli config set export.serviceGroup=pingone
pingcli platform export --output-directory . --overwrite

Important Factoids

The output shows "Resource Type: pingone_forms_recaptcha_v2" returning a 204 No Content response. This is expected behavior as we do not use Recaptcha and have not configured it, but it seems to be related to the hang.

References

None