<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Best Method to Pass Configuration Setting to a GP Service in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/best-method-to-pass-configuration-setting-to-a-gp/m-p/428510#M16564</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AGS / ArcPy Folks:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to determine the best way to pass a configuration setting into a custom geoprocessing service written in Python and published as a service.&amp;nbsp; The class of settings that I'm considering are items that don't change from run to run and potentially sensitive items that I don't think should be passed in as service inputs, ex. database connection string.&amp;nbsp; The best approach I can think of so far is to set a system environment variable to the location of an external (to ArcGIS Server) config file, then write Python to read and parse that config file during each run.&amp;nbsp; Are there other ways to do this?&amp;nbsp; Two main goals are to (1) avoid modifying / republishing the GP service and (2) be straightforward (as possible) for non-developers to manage the configuration settings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Joel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Sep 2015 19:47:54 GMT</pubDate>
    <dc:creator>JoelCarter</dc:creator>
    <dc:date>2015-09-01T19:47:54Z</dc:date>
    <item>
      <title>Best Method to Pass Configuration Setting to a GP Service</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/best-method-to-pass-configuration-setting-to-a-gp/m-p/428510#M16564</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AGS / ArcPy Folks:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to determine the best way to pass a configuration setting into a custom geoprocessing service written in Python and published as a service.&amp;nbsp; The class of settings that I'm considering are items that don't change from run to run and potentially sensitive items that I don't think should be passed in as service inputs, ex. database connection string.&amp;nbsp; The best approach I can think of so far is to set a system environment variable to the location of an external (to ArcGIS Server) config file, then write Python to read and parse that config file during each run.&amp;nbsp; Are there other ways to do this?&amp;nbsp; Two main goals are to (1) avoid modifying / republishing the GP service and (2) be straightforward (as possible) for non-developers to manage the configuration settings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Joel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2015 19:47:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/best-method-to-pass-configuration-setting-to-a-gp/m-p/428510#M16564</guid>
      <dc:creator>JoelCarter</dc:creator>
      <dc:date>2015-09-01T19:47:54Z</dc:date>
    </item>
  </channel>
</rss>

