#  Elements of this map are as below:
    #   o flatDirectoryPackage: (Required - Default '')
    #    This is only for CSharp.
    #    e.g. Aaa.Bbb.DBFlute --> Directory: source/Aaa.Bbb.DBFlute/AllCommon
    #   o omitDirectoryPackage: (NotRequired - Default '')
    #    This is only for CSharp.
    #    e.g. Aaa --> Directory: source/Bbb/DBFlute/AllCommon
    #
    #; outputPackageAdjustmentMap = map:{

# o dbfluteDiXmlPackageName: (NotRequired - Default '../resources')
# o dbfluteDiXmlFileName: (NotRequired - Default 'dbflute.xml')
# o rdbDiXmlResourceName: (NotRequired - Default 'rdb.xml')
#
# {CSharp} Quill(CSharp Seasar) Only:
# o quillDataSourceName: (NotRequired - Default null)
#
# *The line that starts with '#' means comment-out.
#
map:{

    #     (NotRequired - Default Java:'src/main/java' & 'src/main/resources' CSharp:'source')
    #   o sql2EntityOutputDirectory: source output directory from as a relative path from the application directory
    #     (NotRequired - Default Java:'src/main/java' CSharp:'source')
    #
    #; applicationOutsideSqlMap = map:{
    #    ; ../../app1 = map:{

}
# ----------------/
#
# Default mapping as follows:
# --------------------------------------------------------
# | JDBC Type     | Java Native          | CSharp Native |
# | ------------------------------------------------------
# | CHAR          | java.lang.String     | String        |
# | VARCHAR       | java.lang.String     | String        |
# | LONGVARCHAR   | java.lang.String     | String        |

For consistency, the same profiles are used across each chart, even if they do not impact a given chart.

Explicitly set values have highest priority, then profile settings, then chart defaults.

As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
When configuring the chart, you should not include this.

-- simplified configuration
-- multiple versions of the ingress can be used, to minimize upgrade risks

- the new chart uses the default namespace service account, and doesn't require
additional RBAC permissions.

- simplified label and chart structure.
- ability to run a pilot dedicated for the gateway, isolated from the main pilot. This is more robust, safer on upgrades
and allows a bit more flexibility.

-- easier reconfig of just the gateway
-- TLS secrets and domain name management is isolated, for better security
-- simplified configuration
-- multiple versions of the ingress can be used, to minize upgrade risks

- the new chart uses the default namespace service account, and doesn't require
additional RBAC permissions.

- simplified label structure. Label change is not supported on upgrade.

The `values.yaml` API is intended to maintain a *minimal core set of configuration* that most users will use.
For bespoke use cases, [Helm Chart Customization](https://istio.io/latest/docs/setup/additional-setup/customize-installation-helm/#advanced-helm-chart-customization) can be used
to allow arbitrary customizations.

 See the License for the specific language governing permissions and
 limitations under the License.
 .
 On Debian systems, the complete text of the Apache version 2.0 license

        network stack is offline.

  [[3]] "Remote" repositories referenced using the file:// protocol may
        be available. However, if that file:// url references a
        file-share, as in the case of an NFS or SMB mount, that will
        be unavailable.

  So, offline mode has several implications, some of which may not be
  altogether obvious: