Closed BenjaminEngeset closed 3 months ago
Hi @BernieWhite,
Could you please provide some feedback on the work-in-progress code, specifically regarding the rule design/body? I am interested in your thoughts.
Hi again @BernieWhite.
Can you give me some feedback?
I'm still missing the tests, but wanted to check in with you.
Hi @BenjaminEngeset, great progress.
From some additional research, if you are accessing app settings via the
appsettings
named config then the properties can be set via{ }
, otherwise they should be:appSettings: [ { name: 'WEBSITE_NODE_DEFAULT_VERSION' value: '~20 } ]
Great catch! I appreciate you identifying this. I will add in logic for this.
So @BernieWhite, what do you think about the rule now?
I have added test scenarios for several cases, but I have not added cases for sub-resources configured within the parent resource. If you feel that is needed, let me know.
So @BernieWhite, what do you think about the rule now?
I have added test scenarios for several cases, but I have not added cases for sub-resources configured within the parent resource. If you feel that is needed, let me know.
Thanks @BenjaminEngeset Looks look. Yes let's add at least one good and bad case for Microsoft.Web/sites
sub-resources.
I have added a good and bad test case now @BernieWhite.
Following logic:
PR Summary
Working toward #2879
Added Azure.AppService.MigrateNodeJs.
PR Checklist