Greengrass v2 | Component Configuration Cached on Device

I created a new version of a custom Greengrass component and deployed it to my GG core device, which was running the previous version of my custom component.
After the deployment is complete, I noticed that the new component's configuration remained the same as the old component, even though the default configuration has changed in this new version of component. This caused Unauthorized Error since the new access control policies did not get updated.
Was the component configuration cached by the Nucleus? How can I make sure my updates to my custom component updates both the artifact, recipe, and the configuration?