I tried importing the configs of one app1 (specifically for props.conf) to another app2 based on the accepted answer from this Splunk Q&A https://answers.splunk.com/answers/522829/share-propsconf-into-two-different-apps.html
This doesn't seem to import the props from app1 to app2 as desired. I am not getting the field extractions and I do not see the imported props configs in the output of:
/opt/splunk/bin/splunk cmd btool --app=app2 list
I just added the following to /opt/splunk/etc/apps/app2/metadata/local.meta:
 import = app1
Can someone please advise how I can import the field extractions from app1 to app2?
I would suggest copying both, the props.conf as well as the local.meta config file to the new app and only keeping the settings you need. However, there's one question, why do you want to copy it? You could set the sharing to global as well to use the extractions outside of the app.
I'd rather be able to import the configs of the original app, so we only need to update the configs in one place rather than in multiple apps.
Is there a best practice for sharing configs between apps?
The import app functionality isn't really considered a good practice anymore, so there is no other way to do this right now. Well, you still could use the import one but this is not how it is intended to work.