[Feature]: Support externalized catalog config resources

[link3280]

Description

Currently, users need to upload catalog resources like hive-site.xml and keytabs, which would be stored in the AMS home and the database. However, it's cumbersome to maintain 30+ catalogs manually like this. Moreover, it adds to the initiation time of AMS cause a standby/new AMS has to write the resources to the local folders.

We should support externalized resources. For example. AMS catalogs store the hive conf path instead of the content of hive-site.xml. Users using externalized should ensure each AMS instance has access to the resources.

Use case/motivation

No response

Describe the solution

No response

Subtasks

No response

Related issues

No response

Are you willing to submit a PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

[github-actions[bot]]

This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'