title: Using halyard custom profile results in different result from the hal config command
body: <p>I’m trying to setup custom-profiles, with the codes below. However, when I run <code>hal deploy apply</code>, hal says I don’t have persistentStorage configured, and it fails to deploy.</p>
  <pre><code>cat &lt;&lt; EOF &gt;&gt; ./hal/default/profiles/front50-local.yml
  spinnaker:
    s3:
      bucket: my-bucket-spinnaker
      rootFolder: myfolder/front50
      pathStyleAccess: false
      accessKeyId: ID
      secretAccessKey: Key
      enabled: true
  EOF
  
  cat &lt;&lt; EOF &gt;&gt; ./hal/default/profiles/clouddriver-local.yml
  artifacts:
    s3:
      enabled: true
      accounts:
      - name: NAME
        region: ap-northeast-2
  EOF
  </code></pre>
  <p>When I run the code below, I succeed in configuring persistent storage.
  <code>hal config storage s3 edit \ --access-key-id $AWS_ACCESS_KEY_ID \ --secret-access-key $AWS_SECRET_ACCESS_KEY \ --bucket $S3_BUCKET \ --root-folder $CLUSTER/front50</code></p>
  <p>I think the result should be same, but as the prior one doesn’t work, what’s the point using custom-profiles?</p>