-
Notifications
You must be signed in to change notification settings - Fork 32
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
Trying to extract JSON data from an existing MSO controller in order to later design and document a migration to NDO #317
Comments
Enabling debugging shows these 2024-12-18T13:50:47.383-0500 [DEBUG] provider.terraform-provider-mso_v1.3.0: 2024/12/18 13:50:47 [DEBUG] Label: Beginning Creation 405 Not Allowed2024-12-18T13:50:47.558-0500 [DEBUG] provider.terraform-provider-mso_v1.3.0: nginx 2024-12-18T13:50:47.558-0500 [DEBUG] provider.terraform-provider-mso_v1.3.0: 2024-12-18T13:50:47.558-0500 [DEBUG] provider.terraform-provider-mso_v1.3.0: 2024-12-18T13:50:47.558-0500 [DEBUG] provider.terraform-provider-mso_v1.3.0: 2024/12/18 13:50:47 Error occured while json parsing invalid character '<' looking for beginning of value 2024-12-18T13:50:47.566-0500 [DEBUG] State storage *statemgr.Filesystem declined to persist a state snapshot 2024-12-18T13:50:47.566-0500 [ERROR] vertex "mso_label.label1" error: invalid character '<' looking for beginning of value 2024-12-18T13:50:47.573-0500 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF" 2024-12-18T13:50:47.574-0500 [INFO] provider: plugin process |
Sorted this out provider "mso" { in my case the platform needed to be mso |
Hi guys
Here is my main.tf file
This is MSO 3.1.1 and Terrafrom 1.9.8
no matter what I do I am getting an error like below. I initial try to use the import command and I was getting this
Error: invalid character '<' looking for beginning of value
only. After trying to actually create an object I get a little bit more about the line that is causing the error but it is still the same, please see belowWhat could be the reason for the above?
The text was updated successfully, but these errors were encountered: