Error when creating cluster w/o TLS about terraform-aws-eks-jx

[hferentschik]

The generated jx-requirements.yaml looks like this:

autoUpdate:
  enabled: false
  schedule: ""
terraform: true
cluster:
  clusterName: tf-jx-regular-spaniel
  environmentGitOwner: ""
  environmentGitPublic: true
  provider: eks
  region: us-east-1
gitops: true
environments:
  - key: dev
  - key: staging
  - key: production
ingress:
  domain:
  ignoreLoadBalancer: true
  externalDNS: false
  tls:
    email:
    enabled: false
    production: false
kaniko: true
secretStorage: vault
vault:
  aws:
    iamUserName: cjxd-vault
    dynamoDBTable: vault-unseal-tf-jx-regular-spaniel-random19210290120
    dynamoDBRegion: us-east-1
    kmsKeyId: aa295a8f-3845-45bd-8f7b-e8bb8e39428c
    kmsRegion: us-east-1
    s3Bucket: vault-unseal-tf-jx-regular-spaniel-20200330150302388000000004
    s3Region: us-east-1
storage:
  logs:
    enabled: true
    url: s3://logs-tf-jx-regular-spaniel-20200330150303736700000008
  reports:
    enabled: true
    url: s3://reports-tf-jx-regular-spaniel-20200330150302388500000005
  repository:
    enabled: true
    url: s3://repository-tf-jx-regular-spaniel-20200330150302390300000007
versionStream:
  ref: master
  url: https://github.com/jenkins-x/jenkins-x-versions.git
webhook: prow

[hferentschik]

On a side note vault-unseal-tf-jx-regular-spaniel-random19210290120 is the string "random" intendented?

[dgozalo]

On a side note vault-unseal-tf-jx-regular-spaniel-random19210290120 is the string "random" intendented?

It was a workaround I did to get past the creation, I probably should fix that.

[hferentschik]

🎉 This issue has been resolved in version 0.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀