get outputs when using the cloudformation create/update task

[jeffrey-opdam]

Hi guys,

When using the cloudformation create/update task, you will get the stackid as an output variable.
Is it also possible to get the outputs as defined in the yml file?

Outputs: InstanceId: Description: InstanceId of the newly created EC2 instance Value: !Ref EC2Instance AZ: Description: Availability Zone of the newly created EC2 instance Value: !GetAtt - EC2Instance - AvailabilityZone PublicDNS: Description: Public DNSName of the newly created EC2 instance Value: !GetAtt - EC2Instance - PublicDnsName PublicIP: Description: Public IP address of the newly created EC2 instance Value: !GetAtt - EC2Instance - PublicIp

[stevejroberts]

Apologies for the delay in responding; combination of vacations and team focus elsewhere for the moment :-)

It's certainly possible, how would you want to consume the outputs? As a series of build variables, or a formatted blob of yaml/json that you'd need to parse?

[jeffrey-opdam]

As a series of build variables, so I have the fqdn name, which I later can use in my deployment

Build vars would be awesome but also json output would be handy too, could help with cross-region workloads.

[stevejroberts]

Ok, I'll see what we can get done but I can't promise any specific ETA right now. Of course, we're also always happy to take pull requests!

Tempted to start contributing, is there a into guid for developing on the VSTS / ADO platform ?

…

On 2 Oct 2018, at 20:53, Steve Roberts ***@***.***> wrote: Ok, I'll see what we can get done but I can't promise any specific ETA right now. Of course, we're also always happy to take pull requests! — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[stevejroberts]

We don't (yet) have a contributing guide in the repo but all our tasks are reasonably standardized in how we put them together so extending one to add some new parameters is relatively easy. The tricky bit is in testing; we used to be able to use a launch config entry in VSCode during development to simulate supply of the credentials and parameters into the task but with recent updates we're finding this no longer works and haven't had time to find the root cause yet. We (at AWS) are currently reliant on a Team Foundation Server instance running integration tests to verify our changes, which obviously isn't suitable for long term open source contributions.

The general development guidelines for the host environment can be found here.

In the absence of a formal contributing doc and unit test setup, I'd be happy to help guide a contribution if you want to give it a try (and also help with testing).

[manishap411]

Has this change been released? or is there a timeline for when this could roll out? Thanks!

[hunterwerlla]

This is fixed as of the 1.2.0 release we just did, @manishap411 @jeffrey-opdam