Allows for users to supply a pass-through value for fog_aws_storage_options to configure whatever they so desire for the fog connection to an S3 blobstore. This PR should be safe to merge and run against cf-for-k8s develop since it defaults to an empty hash just as it was before.
In order to actually expose this configuration to CF operators, you would have to do one of the following:
Add changes to cf-for-k8s to expose that configuration in their install values file and provide a modified values file like so:
Allows for users to supply a pass-through value for
fog_aws_storage_options
to configure whatever they so desire for the fog connection to an S3 blobstore. This PR should be safe to merge and run againstcf-for-k8s
develop since it defaults to an empty hash just as it was before.In order to actually expose this configuration to CF operators, you would have to do one of the following:
Add changes to cf-for-k8s to expose that configuration in their install values file and provide a modified values file like so:
Make no changes to cf-for-k8s and require that operators supply an additional data values file when deploying CF like so:
and deploy with that additional values file:
kapp deploy -a cf -f <(ytt -f config/ -f install-values.yml -f that-additional-data-values-file.yml)