-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New-AzManagedApplication - Object reference not set to an instance of an object #12042
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure. |
I include Managed Applicatoins team to look into this issue. |
We had an incident at this time that should be resolved and allow this to succeed. Could you please confirm if this has been resolved? |
@MSEvanhi No, the exact same error comes up when we attempted this again |
@wahyuen we are actively looking into this issue as an incident. We should be able to provide an update in the next few days. |
@MSEvanhi just wondering if there was any update to this issue? |
Hey @wahyuen , are you passing in parameters using -parameters and following this json format? Unfortunately that error message will show if this is the case as well. I want to make sure we're passing in parameters and still getting this error message. We concluded the incident and it would not have caused this issue. |
@MSEvanhi It appears the error occurs no matter what I put in the -Parameter value. We updated the command to have the following format: -Parameter "{`"environment`": {`"value`": `"vnet`"}}" and verified that the 'deployment' had the same value being passed in via the Azure Portal Deployment blade..but the |
@MSEvanhi Just checking in to see if there were any updates on this issue? |
I'm going to see if we can investigate with engineering here, but honestly that may take awhile. I would attempt to workaround this in the mean time using a parameter file or variable like in the documentation I provided. I still think that we're passing parameters incorrectly here, as I cannot get your syntax to work on my side... |
@MSEvanhi An update on our side, we have since removed the parameters all together from the deployment and we still have the exact same error. Of note, since we have reworked to remove the parameter, the 'Deployment' on the Azure Managed Resource Group actually indicates it successfully deployed, however the 'Managed App' did not appear. NB. these tests were run on v5.1.0 of Az Powershell |
Description
When attempting to create a new Managed Application, the command returns with
Object reference not set to an instance of an object
Steps to reproduce
Environment data
Module versions
Debug output
Error output
The text was updated successfully, but these errors were encountered: