[FEATURE REQUEST] optional namespace for http_json external pillar data

[ctramnitz]

Is your feature request related to a problem? Please describe.
I'm trying to import external data that is not under my authority as ext_pillar via http_json. However, the resulting data is imported in the pillar root, which is both inconvenient and (since I have no authority over the external data structure) may pollute the pillar.

Describe the solution you'd like
Similar to csvpillar I would like to see an optional namespace that can be prepended so that the external pillar data is imported under s specified subkey.

Describe alternatives you've considered
I considered writing a formula. But since the same option already exists in csvpillar it may be worthwhile to have it for http_json too.

[welcome]

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

• Community Wiki
• Salt’s Contributor Guide
• Join our Community Slack
• IRC on LiberaChat
• Salt Project YouTube channel
• Salt Project Twitch channel

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at [email protected]. We’re glad you’ve joined our community and look forward to doing awesome things with you!