Pseudo parameters no longer work in custom variables or resources

[adsurg]

The earlier evaluation means that "#{AWS::StackName}-lock" is no longer being substituted. This is working in v1.3.2.

resources:
  Resources:
    lambdaLockDb:
      Type: 'AWS::DynamoDB::Table'
      ...
      TableName: "#{AWS::StackName}-lock"

provider:
  name: aws
  ...
  environment:
    LOCK_TABLE: ${self:custom.lockTableName}
custom:
  lockTableName: "#{AWS::StackName}-lock"

[svdgraaf]

Ok, yeah, that's not good. Perhaps I should start adding tests ;)
I'll see if I can fix this, not sure if I have time today though.

[adsurg]

That was my reaction :-). I thought I'd have a look at fixing this, but the lack of tests made me fearful of just breaking your previous issue. Cheers for replying so quickly.

[komushi]

Had the same issue now with #{AWS::Region} under resource.
I was using 1.1.5 and it was working.

[adsurg]

Version 1.3.2 is the same as v1.4, but without this change. We've stopped at that version for now.

[komushi]

Thanks. Will fix it to 1.3.2 for now

[lorengordon]

Submitted #11 with a patch for this issue

[svdgraaf]

Thanks @lorengordon!
@adsurg I just released 1.4.1, can you check whether that fixes your issues?

[adsurg]

Thanks @lorengordon!
That's done the job nicely

[svdgraaf]

Ok, closing this one :)