feat(flags): Add method for fetching decrypted remote config flag payload

[havenbarnes]

Context: https://github.com/PostHog/posthog/pull/27414/files

[greptile-apps]

PR Summary

This PR adds functionality to fetch decrypted remote config flag payloads through new methods in the PostHog Python client, enabling secure access to flag configurations.

• New remote_config function in /posthog/request.py needs correction in success message and parameter validation
• Added get_decrypted_feature_flag_payload method in /posthog/__init__.py requires improved documentation for parameters and return types
• Implemented get_remote_config_payload in /posthog/client.py with personal API key validation and error handling
• API endpoint path construction in /posthog/request.py could be improved for better clarity
• Missing type hints for new methods across all modified files

_{3 file(s) reviewed, 7 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Success message should be specific to remote config, e.g. 'Remote config fetched successfully' instead of reusing 'Feature flags decided successfully'

[dmarticus]

i agree with greptile here

[haacked]

Just so I understand, decryption always happens on the server, correct? And it looks like there's an API endpoint to get a single decrypted setting, but not a way to get all of them?

[havenbarnes]

Just so I understand, decryption always happens on the server, correct?

Correct!

And it looks like there's an API endpoint to get a single decrypted setting, but not a way to get all of them?

Yes, the /remote_config endpoint is intended for single decrypted settings. However our GET /feature_flags ("list all flags") endpoint would also decrypt feature flags for you if you were authenticated with a personal API key, so you could get all of them at once if you wanted to