Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pulumi is not triggering configured Instance Refresh after Lanuch Template update.

See original GitHub issue

In the pulumi AWS Auto Scaling Group input, there is option to configure triggering Instance Refresh after events like launch template update etc.

The documentation says that if the instanceRefresh block is configured then pulumi will start the Instance Refresh. However, I am not observing this behaviour after updating the lunch template, and I need to trigger it from the console manually.

Steps to reproduce

I’ve created a simple deployment in pulumi node.js to help you reproduce this scenario, link. There you have detailed reproduction steps etc. However basically, to reproduce:

Launch a deployment containing Auto Scaling Group with instanceRefresh option configured and Launch Template.
Change sth in the Lauch Temple.
Run the deployment again, the pulumi should update the launch temple.
Open AWS console, go to ASG section and check that instance refresh was not triggered, despite the documentation says:

A refresh will always be triggered by a change in any of launch_configuration, launch_template, or mixed_instances_policy.

Expected: Pulumi should trigger Instance Refresh procedure on ASG Actual: The Instance Refresh is not triggered

Tested on: Pulumi: v3.7.0 Node: 12.x and 15.x

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

emilizacommented, Jul 23, 2021

Ah, sorry about that - I missed the README in the repo and was going just on the comments in this issue.

I’m able to repro with your repo - also tried making a few edits forcing the updateDefaultVersion in launchTemplate, to no avail - seems like a bug within our aws provider; I’ll also be transferring this issue to the correct repo

0reactions

dimitor115commented, Sep 8, 2021

@leezen Thank you! I can confirm that the solution you have described works for me 😄

Top Results From Across the Web

Troubleshooting Guide - Pulumi

This guide covers common troubleshooting techniques when using Pulumi, such as tracing, manually editing deployments, and resolving common errors.

aws.autoscaling.Group - Pulumi

If this block is configured, start an Instance Refresh when this Auto Scaling Group is updated. Defined below. launchConfiguration string | LaunchConfiguration.

Configuring AWS Auto Scaling | Crosswalk - Pulumi

Pulumi Crosswalk for AWS allows you to easily to define Auto Scaling Groups (ASGs) to configure scaling of EC2 instances.

Module autoscaling | Package @pulumi/awsx | Node.js SDK

A launch configuration is an instance configuration template that an Auto Scaling group uses to launch EC2 instances. When you create a launch...

aws.ec2.LaunchConfiguration - Pulumi

Launch Configurations cannot be updated after creation with the Amazon Web ... on the Launch Configuration which will attempt to reserve your instances...