Policy regarding Anonymous and Admin users updates

Hi,

I've been trying to figure out a way to deploy a Drupal instance from scratch, without using any database dump, and relying solely on config and content import.

So far, my approach has been.

1. drush site:install
2. override site uuid to match configuration uuid.
3. override site admin and anonymous default users, to match the content sync admin and anonymous users. ( I do this using custom bash scripts, to parse, and find the corresponding uuids ).
4. drush pm:enable content_sync ( enable content_sync manually, so we make sure the snapshot gets generated ( see https://www.drupal.org/project/content_sync/issues/3134102 🐛 Content Snapshot not populated when installing from configuration Needs review ).
4. drush cim ( configuration import ).
5. import content.

The first issue i am having, is that i am not able to identify which one is the admin user. There is a metadata tag for is_anonymous, but not for the admin one.

I understand the policy for those users, are to not override the content for those users, but that policy does not help with the type of workflow described above. I believe this could be added as a setting, and allow the user to decide and be able to import changes from those users. This way, it can help people using with this type of workflow.

As a summary, my proposal goes in the lines of:

1. Add a metadata is_admin to user with uid 1, during content export.
2. Add a setting, to allow / disallow to import content from admin and anonymous users.

In case the setting is disabled:
- Do not show those users as changes to import ( currently, it shows in the change list as "update", but it is never updated, so it stays like this forever.

In case the setting is enabled:
- Import the user changes as with the rest of the content to import.

Any opinions about this, any better ways to approach the problem ?
Are you implementing this kind of workflow in a different way ?
I will wait a few days to see if we can come up with a better idea, and develop the mentioned functionality.