Further Expose Secrets Manager Auto Registration Settings

[pwortas]

Currently, configure_secrets_management_auto_registration() only accepts a SubnetSelection when determining which networks to add to the identity auto registration.

In a hybrid environment, we have workers coming up in subnets not managed by RFDK or not in AWS at all. It would be nice to be able to provide a list of additional CIDR so that we can keep our repo configuration fully in code and not require post-deployment clickops.

Use Case

1. Deploy an RFDK farm from code.
2. Add on-prem workers.
3. Worker subnets require manual configuration of the identity management backend.

Proposed Solution

Add the ability to cumulatively append subnets to the configuration prior to deployment that does not rely on ISubnet or SubnetSelections. A new prop could be possibly constructed that takes a status, a role and the cidr as a string.

---

This is a 🚀 Feature Request

[jusiskin]

Thanks for submitting this feature request @pwortas. This seems like a useful enhancement for RFDK users. We have added this to our backlog and report here when we have updates.