Managed account variable causing error

Legacy Cloud
1

Steps to reproduce:

  1. Set up a managed AWS account
  2. Set up a terraform project
  3. Click process » managed account » AWS Account » Try to set a variable

Result:


in _
in WithValidateOnChange(_)
in WithProjectVariables(WithValidateOnChange(_))
in div
in n
in div
in div
in div
in t
in div
in div
in t
in t
in t
in n
in Connect(n)
in div
in t
in div
in div
in t
in t
in t
in div
in div
in div
in t
in div
in div
in t
in div
in div
in n
in div
in t
in div
in t
in n
in t
in withRouter(n)
in n
in Connect(n)
in n
in t
in t
in t
in t
in t
in t
in div
in div
in MediaQuery
in div
in Unknown
in t
in withRouter()
in main
in t
in Connect(t)
in t
in t
in t
in t
in t
in t
in withRouter(t)
in t
in t
in t
in t
in t
in r
in t
in t
in t
in t
in t
in Unknown
in div
in t
in Connect(t)
in t
in t
in t
in t
in t
in t
in t
in t
in Provider
in t
in Unknown
in t

HIDE FULL EXCEPTION

Octopus v2018.11.1

TypeError: Cannot read property 'map' of undefined

map (/app/components/form/VariableSelect/VariableSelect.tsx:57:35)
beginWork (/node_modules/react-dom/cjs/react-dom.production.min.js:149:336)
e (/node_modules/react-dom/cjs/react-dom.production.min.js:182:349)
g (/node_modules/react-dom/cjs/react-dom.production.min.js:183:347)
p (/node_modules/react-dom/cjs/react-dom.production.min.js:184:366)
batchedUpdates (/node_modules/react-dom/cjs/react-dom.production.min.js:190:255)
injectFiberControlledHostComponent (/node_modules/react-dom/cjs/react-dom.production.min.js:41:336)
injectFiberControlledHostComponent (/node_modules/react-dom/cjs/react-dom.production.min.js:41:270)
batchedUpdates (/node_modules/react-dom/cjs/react-dom.production.min.js:42:77)
Cb (/node_modules/react-dom/cjs/react-dom.production.min.js:45:158)
2

Hi Stuart, thanks for getting in touch,

We are aware of this issue and will be releasing the fix as part of 2018.11.2 early next week. I would like to apologize for any inconvenience this may have caused you. Your existing deployments should continue to work, however editing or adding a new step may cause some problems until then.

Since you are using an AWS account as part of a Terraform step, you should be able to bind the properties of the AWS accounts as part of your template instead of choosing an AWS account directly in the interim i.e:

provider "aws" {
  access_key = "#{awsaccount.AccessKey}"
  secret_key = "#{awsaccount.SecretKey}"
  region     = "us-east-1"
}

Regards,
Shaun