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
Resource Import Issues, Including APIM - Need Clarification #470
Labels
question
Further information is requested
Comments
Hi @gogo25171, I'm answering your questions as following:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone,
I recently attempted to import Azure resources, particularly APIM, using Azure Terrafy, but I encountered some difficulties. I'm wondering if there are any known limitations or issues that could explain why this import is not working as expected.
I'd like to request community assistance to clarify a few points. Here are some assumptions I have in mind, but I'm open to other insights:
Running Resource Issues: Could there be import problems when the Azure resource, like APIM, is in a running state or has states that make import challenging?
Complexity and Dependencies: Can complex resources with many dependencies pose import issues? Are there any guidelines for managing such situations?
Resource Support: Does Azure Terrafy currently not support certain Azure resources, including APIM? If so, is there a timeline for updates to add these features?
Other Issues: Are there any other factors or problems that I may not have considered?
I appreciate any assistance, information, or examples of successful use cases. This will not only help me but also other community members who may encounter similar issues.
Thank you in advance for your help!
Best regards
The text was updated successfully, but these errors were encountered: