feat: Add lifecycle ignore userdata as otherwise reboots existing instances #411
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add instance Lifecycle rule to ignore user_data changes.
Motivation and Context
There are times when I want to update the userdata and not replace the existing instances (which can be achieved with user_data_replace_on_change) but also not reboot the existing instances which is the case if not replaced. We can't be rebooting tens of instances for a small change we want applied to any new instances and if we want it applied to all instances then a replace is required anyway
Breaking Changes
No
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request