When doing an upgrade on FME Cloud through backup/restore (backup instance1, create instance2, restore .fsconfig file from instance1 on instance2) the target url's for push subscriptions are not updated, so they are still pointing to instance1 after the restore. It would be useful to have an option on the restore process that updates those target url's if they are pointing to the "local" instance.
Archived
Backup and Restore: update push subscription target url
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+9- Safer
Moving to FME Server as this is an issue that would need fixing on the FME Server codebase.
+14- Safer
I think this is where the FME Workspace Subscription is useful - though, understandably, not convenient if dealing with pre-FME Workspace Subscription installations of FME Server..