Move to "Package"

[ChuckJonas]

Options

Unmanaged (no package)

Pros

• path of least resistance (this is how things work)

Cons

• Cannot install
• Cannot "depend on" with from packages
• Upgrade process less straight-forward
• cannot implement Add Encrypted Type #4

Unlocked without namespace

Pros

• get an install url / id
• can upgrade over existing versions without needed to migrate
• Full transparency of code.
• Installers can make changes in org if they really need to (not a good idea tho)
• upgradable

Cons

• cannot implement Add Encrypted Type #4
• could cause conflicts with unmanaged code (if they already have ENV.cls class or Env_Var__mdt

Unlocked with namespace

Pros

• No concern with overwriting metadata
• get an install url / id
• Full transparency of code.
• Installers can make changes in org if they really need to (not a good idea tho)
• upgradable

Cons

• will need to migrate anyone whose installed in unmanaged space (pretty minimal effort, could provide script to copy mdt from one namespace to other)
• cannot implement Add Encrypted Type #4

Managed Package

Pros

• No concern with overwriting metadata
• get an install url / id
• can implement Add Encrypted Type #4
• upgradable

Cons

• full transparency of code.
• will need to migrate anyone whose installed in unmanaged space (pretty minimal effort, could provide script to copy mdt from one namespace to other)
• Notoriously more challenging to upgrade / make changes / depreciate

Unlocked Package & Managed Package in same namespace

Pros

• No concern with overwriting metadata
• get an install url(s) / id(s)
• can implement Add Encrypted Type #4
• Would allow us to put support for Add Encrypted Type #4 in a managed package but keep the rest of it "unlocked" which makes it easier to manage
• upgradable

Cons

• have to install two separate packages (maybe there is someway to make the unlocked package install the managed package automatically?)
• full transparency of code (except Add Encrypted Type #4).
• will need to migrate anyone whose installed in unmanaged space (pretty minimal effort, could provide script to copy mdt from one namespace to other)

[ChuckJonas]

I'm thinking that Unlocked Package & Managed Package in same namespace is the current route.

We can use a soft dependency (using callable) on the env-vars-encrypt managed package which will allow us to provide the capability, optionally, if the user wants to install it.

The biggest downside is the need to migrate data, apex, formulas...

However, I think we can provide a method to make it easy to copy over the ENV vars. (plus who is actually using this beside me?)