Approve auth method creation strategy?
What should be the approve auth method creation strategy?
Scenario: I'm working for a company many machines and apps(let's say jenkins) need to retrieve some secrets and run some apps and complete a workflow. think that I have many apps and machines. in this case what should be the approle creation and structuring strategy? based on app, based on team or totally random, or any other? is there any limitation? any other method can replace approve method? since this is kind of user,pwd. you're configuring and then using it? is there a method to rotate rolled or secretid? pros/cons? in which cases should this method opt for?