I want to deploy a new feature to my existing Forge app with existing users.
This new feature requires an additional egress permission. While the feature will be a useful addition, I consider it non-core.
Is there a way to make this feature available to new users, but not existing ones? I don’t want to bother the latter with a permission update for a feature that I consider optional.
Essentially I’d like to have two user cohorts (pre new feature, and post new feature) and be able to deliver future fixes/improvements that unrelated to the new feature to both cohorts.
From what I can tell, I can achieve (1) by running
forge deploy but not
forge install --upgrade. But then I won’t be able to satisfy requirement (2).
How can I do both (1) and (2)?