Khetha kuqala igatsha le-constructor. Uma i-simple-salesforce yakha i-Requests Session yayo, sebenzisa ukuhlela kwayo okusobala proxies. Uma unikeza i-Session, leyo nto inepulazi lomzila futhi ukuhlela okuhlukile kuyashaywa indiva ngesixwayiso.

Nge-token ne-instance URL esekhona, igatsha le-Session elijwayelekile yile:

from simple_salesforce import Salesforce

sf = Salesforce(
    instance_url='https://org.example.my.salesforce.com',
    session_id=access_token,
    proxies={'https': 'http://proxy.example:8080'},
)

Sebenzisa i-instance yangempela ye-Salesforce kanye ne-access token. Inani liyingxenye ye-HTTP yezingcingo ze-HTTPS API. Emkhakheni womphakathi ovunyelwe we-Salesforce endpoint ngaphandle kokuqinisekiswa kwe-proxy, umbhalo ovela kuhlu lwama-proxy e-HTTP ungahlinzeka leyo URL; i-token ye-Salesforce ihlala ihlukile. Ekungeneleleni okuqhutshwa yi-constructor, nikela ukuhlela ngesikhathi kwakhiwa ukuze umsizi wokungena akuthole ngaphambi kokuthola i-Session.

Nge-Session yangokwezifiso, yilungise ngqo:

import requests

session = requests.Session()
session.proxies.update({'https': 'http://proxy.example:8080'})
sf = Salesforce(
    instance_url=instance_url,
    session_id=access_token,
    session=session,
)

Ukuziphatha okujwayelekile kwendawo ye-Requests yento yangokwezifiso kuhlala kusebenza. Gcina lowo mzila endleleni ye-constructor esetshenziswa yi-SDK; ukulungisa iklayenti elihlukile eceleni kwayo akukuthinti lezi zingcingo.

Izihloko ezihlobene