README.md in kubes_google-0.1.1 vs README.md in kubes_google-0.1.2

@@ -27,20 +27,20 @@
 
 Then set the secrets in the YAML:
 
 .kubes/resources/shared/secret.yaml
 
-```
+```yaml
 apiVersion: v1
 kind: Secret
 metadata:
   name: demo
   labels:
     app: demo
 data:
 <% KubesGoogle::Secrets.data.each do |k,v| -%>
-  <%= k %>: <%= Base64.encode64(v).strip %>
+  <%= k %>: <%= base64(v) %>
 <% end -%>
 ```
 
 This results in Google secrets with the prefix the `demo-dev-` being added to the Kubernetes secret data.  The values are automatically base64 encoded.
 
@@ -76,9 +76,10 @@
 
 Secrets#initialize options:
 
 Variable | Description | Default
 ---|---|---
+base64 | Automatically base64 encode the values. | false
 upcase | Automatically upcase the Kubernetes secret data keys. | false
 prefix | Prefixed used to list and filter Google secrets. IE: `projects/686010496118/secrets/demo-dev-`. Can also be set with the `GCP_SECRET_PREFIX` env variable. The env variable takes the highest precedence. | nil
 
 Note, Kubernetes secrets are only base64 encoded. So users who have access to read Kubernetes secrets will be able to decode and get the value trivially. Depending on your security posture requirements, this may or may not suffice.