Update about Autofill improvements in Beta

Hi all, not sure if 1P is still listening to these threads 1P_Travis , but I want to first thank you for the functionality, and I appreciate how quickly you were able to get this work done in the beta.

I'm going to make an assumption that many of the users who want this feature would be of the following personas:
* Technical users (developers or PMs)
* Migrating from a competitor

and if so, their use cases fall into one of a few buckets:
* 1) They have a handful of cases where this is useful, but are happy with the default behavior.
* 2) They have many cases (in some cases maybe an entire Vault) where they want to change all at once.
* 3) They need to customize the behavior across a variety of different entries.

Your current solution addresses bucket #1.

For bucket #2, it is also likely that it's a one-time operation, and that future items might benefit from a default, but could be managed on a 1 by 1 basis after the initial batch processing.

For bucket #3, customization for technical users is best done at the API level, if it's done at all as this is likely only a handful of highly technical users who have this case.

Given this, I strongly recommend, regardless of what you might want to do with the feature in the future that you at minimum expose the current autofill override functionality to the CLI, so that your technical users can either write a simple loop to apply to a subset of items, or can configure their own logic to determine which ones should have the logic and which ones should not. For non-technical users who are migrating from a competitor, my guess is they'll land on a support forum like this, and a more experienced user can explain (or even provide) a script that does what they want.

Without this, at the moment it's just a painful transition for people such as myself who have had this feature for years in a competitor offering.

Thanks!