Google Cloud DLP Python: saita tushen amincewa don gRPC
Saita GRPC_DEFAULT_SSL_ROOTS_FILE_PATH kafin ƙaddamarwa don hanyar zaɓin tushe ta tsoho, ba tare da dogaro da zirga-zirgar alamar Requests ba.
GRPC_DEFAULT_SSL_ROOTS_FILE_PATH=/path/to/approved-roots.pem \
https_proxy=http://proxy.example:8080 \
python dlp_job.pyYi amfani da tarin PEM da ke ɗauke da saitin tushen da ake buƙata don wuraren ƙarshen gRPC, gami da tushen ƙungiya da na jama'a da suka dace. Don gwaji mara mahimmanci a kan wuraren ƙarshen DLP na jama'a inda aka yarda da wakilai na jama'a, jerin wakilai na HTTP yana bayar da 'yan takara don https_proxy; riƙe tushen da aka amince da su da tsarin shaidar aikace-aikacen. Ba a ɗauka cewa fayil ɗin tushen tsoho yana ƙara kansa zuwa kowane ajiya na dandali.
Wannan yana aiki lokacin da DlpServiceClient ke amfani da tushen tsoho na jigilar gRPC. Idan tashar ta bayar da takaddun tushe bayyananne, duba shaidar wannan tashar maimakon. Saitin CA na Requests na iya gyara kiran HTTP ba tare da canza wannan tushen amincewar gRPC ba.
Karanta matakin da ya kasa daban daga tushen da aka zaɓa. Wakili mara samuwa ko CONNECT da aka ƙi yana faruwa kafin binciken takardar wurin da za a je na gaba kuma ba a gyara shi ta ƙara CA.
Samun alamar shaidar na iya amfani da wani abokin ciniki na HTTP. Ba wa wannan hanyar tsarin CA da ake tallafawa idan tana buƙatar wannan ikon, tare da riƙe tabbaci a kan haɗin biyu.