Resource refresh when creating a new version| View in Tracker
In a production environment where you want to test and deploy new/updated resources, you need some way to retain a test and production configuration. Creating a new API with the same name but a different version loses all existing subscriptions and API keys. Updating an API using the new version feature retains the subscriptions and API keys but does not see resource definition changes. When creating a new version of an API, you must manually enter any changes to the arguments or resource names. This is tedious, error prone, and time consuming but does allow the configuration to remain. When creating a new version, it would be desirable to have the API Manager reload the resource definitions from the CF instance when the API was initially defined. Existing subscriptions and applications would remain the same, but the publisher would need to update the SLA's and authentication settings for new resources.