You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to deploy connected apps using the Salesforce CLI, you have to delete the consumer key line manually or else the deployment will fail because the key is unique in each org until you do a refresh.
I had to write a custom script to automatically delete the consumer key lines in every consumer app meta file before starting a deployment with connected apps. This works to deploy apps to multiple orgs with the other settings the same (previously I just had to instruct our developers to manually delete the line after retrieval).
The Salesforce CLI should be updated to not include the consumer key when retrieving connected apps from an org so the files will be deployable automatically after retrieval.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_connectedapp.htm
In order to deploy connected apps using the Salesforce CLI, you have to delete the consumer key line manually or else the deployment will fail because the key is unique in each org until you do a refresh.
I had to write a custom script to automatically delete the consumer key lines in every consumer app meta file before starting a deployment with connected apps. This works to deploy apps to multiple orgs with the other settings the same (previously I just had to instruct our developers to manually delete the line after retrieval).
The Salesforce CLI should be updated to not include the consumer key when retrieving connected apps from an org so the files will be deployable automatically after retrieval.
Beta Was this translation helpful? Give feedback.
All reactions