remove deprecated resources #602
Conversation
Signed-off-by: Sathish <sbabu@progress.com>
sathish-progress
added
do not merge
Version: Bump Minor
Signed-off-by: Sathish <sbabu@progress.com>
Signed-off-by: Sathish <sbabu@progress.com>
Signed-off-by: Sathish <sbabu@progress.com>
Signed-off-by: Sathish <sbabu@progress.com>
Signed-off-by: Sathish <sbabu@progress.com>
Signed-off-by: Sathish <sbabu@progress.com>
Signed-off-by: Sathish <sbabu@progress.com>
Signed-off-by: Sathish <sbabu@progress.com>
|
Kudos, SonarCloud Quality Gate passed!
|
|
Are these going to be deprecated or EOL'd? Either way we need to update our documentation on https://docs.chef.io/inspec/resources/ |
|
Nice! |
|
Approved. Is there more changes pending? Asking because there is a label "Do Not Merge" |
|
I think we've got to be careful with this. All of the azurerm resources are listed here: https://docs.chef.io/inspec/resources/#azure There's no notice under any of them that they're deprecated or when they will be EOL and so there may be people using them. It could create problems if these get yanked all of a sudden. |
@IanMadd , can we update that docs saying that it would be deprecated starting v2? |
@sathish-progress We can. Is there a deprecation date or EOL date? |
I don't have a date for now.. but when we are at 2.0 we can release them |
Signed-off-by: Deepa Kumaraswamy <dkumaras@progress.com>
❌ Deploy Preview for inspec-azure failed.
|
| @@ -400,14 +400,15 @@ The behavior of the http client can be defined with the following parameters: | |||
|
|
|||
| They can be defined as environment variables or resource parameters (has priority). | |||
|
|
|||
| <hr> | |||
| {{< warning >}} | |||
There was a problem hiding this comment.
@dkumaras The {{< warning >}} shortcodes only work in Hugo, not in GitHub.
Signed-off-by: Sathish sbabu@progress.com
Description
remove deprecated resources
release as part V2
Issues Resolved
#600
Check List
rake lintpasses