You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2024. It is now read-only.
Few weeks ago it was decided not to include delicense code in asg module, but now when we are adding this behaviour for GCP in PR 191, then similar feature should be available in AWS.
Describe the solution you'd like
add option for asg module to enable or disable delicense FW by Lambda
add Python function to do delicense
Describe alternatives you've considered.
Plugin sw_fw_license enable delicensing after N hours, where 1 <= N <= 24 hours. For some use case event based approach (just after scale in) is preferred one (instead of waiting at least 1 hour).
Additional context
After delivering PR for that issue customer will have a choice:
use event based approach and delicense just after scale in
do not use additional Python code in Lambda and wait at least 1 hour to delicense removed FW
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Few weeks ago it was decided not to include delicense code in
asg
module, but now when we are adding this behaviour for GCP in PR 191, then similar feature should be available in AWS.Describe the solution you'd like
asg
module to enable or disable delicense FW by LambdaDescribe alternatives you've considered.
Plugin
sw_fw_license
enable delicensing after N hours, where1 <= N <= 24 hours
. For some use case event based approach (just after scale in) is preferred one (instead of waiting at least 1 hour).Additional context
After delivering PR for that issue customer will have a choice:
The text was updated successfully, but these errors were encountered: