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
Is this feature request related to a new rule or cfn-lint capabilities?
No response
Describe the feature you'd like to request
When using a deprecated run time, we can either receive an error message or ignore the error message. To avoid ignoring the message and missing all deprecation notices, if we could instead receive an informational message in its place, we can maintain awareness of the issue without it becoming a blocker due to the error message.
Describe the solution you'd like
To avoid ignoring the Error message and missing all deprecation notices, if we could instead receive an informational message in its place, we can maintain awareness of the issue without it becoming a blocker due to the error message.
Additional context
No response
Is this something that you'd be interested in working on?
👋 I may be able to implement this feature request
Would this feature include a breaking change?
⚠️ This feature might incur a breaking change
The text was updated successfully, but these errors were encountered:
cloudgenie101
changed the title
Instead of deprecation warning, have an option to recieve informational message.
Instead of deprecation warning, have an option to recieve an informational message.
Sep 5, 2024
Is this feature request related to a new rule or cfn-lint capabilities?
No response
Describe the feature you'd like to request
When using a deprecated run time, we can either receive an error message or ignore the error message. To avoid ignoring the message and missing all deprecation notices, if we could instead receive an informational message in its place, we can maintain awareness of the issue without it becoming a blocker due to the error message.
Describe the solution you'd like
To avoid ignoring the Error message and missing all deprecation notices, if we could instead receive an informational message in its place, we can maintain awareness of the issue without it becoming a blocker due to the error message.
Additional context
No response
Is this something that you'd be interested in working on?
Would this feature include a breaking change?
The text was updated successfully, but these errors were encountered: