Access to metadata in tags?

[lox]

I'm trying to access the local tags used in some YAML I'm parsing:

  LaunchConfiguration:
    Type: AWS::AutoScaling::LaunchConfiguration
    Properties:
      AssociatePublicIpAddress: true
      InstanceMonitoring: true
      SecurityGroups: [ $(InstanceSecurityGroup) ]
      ImageId: $(AWSRegionToAMI[$(AWS::Region)][AMIID])
      InstanceType: $(InstanceType)
      IamInstanceProfile: $(EC2InstanceProfile)
      KeyName: $(KeyName)
      UserData: !Base64 |
        #!/bin/bash -xve
        yum install -y aws-cfn-bootstrap
        /opt/aws/bin/cfn-init -v --stack $(AWS::StackName) --resource LaunchConfiguration --region $(AWS::Region)
        /opt/aws/bin/cfn-signal -e \$? --stack $(AWS::StackName) --resource ECSAutoScalingGroup --region $(AWS::Region)

I'm specifically interested in accessing the !Base64 local tag, which seems to be dropped when parsing. Is there any way to get access to it?

[aelsabbahy]

Did you ever find an answer to this?

[lox]

Nope, unfortunately not.

…

On Fri., 9 Dec. 2016 at 9:59 am, Ahmed Elsabbahy ***@***.***> wrote: Did you ever find an answer to this? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#150 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA9jhhjmDrMUD3ijVT_CvyraiGgXau8ks5rGIvegaJpZM4Gto9F> .

[niemeyer]

This will be sorted in the on going v3 work.

[svyotov]

@niemeyer when should we expect v3 and is there a place were we can access it now even in a dev stage?

[niemeyer]

@svyotov I've been working on it (actually, on the package that depends on the new features, which is my guideline), and hope to get the release out before the EOY.

[fgimian]

Hey @niemeyer, thanks so much for your work on this package.

I couldn't seem to see a v3 branch in this repository. Is there somewhere we can check out your progress on v3 and try out an early version? 😄

Thanks heaps
Fotis

[lox]

Might be worth pinning an issue relating to v3 at the top of issues @niemeyer?

@fgimian it's not available anywhere, and won't be until it's ready, based on previous feedback from @niemeyer!

[fgimian]

No worries @lox, thanks for the reply 😄