You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
We have created our own operators (e.g for AWS RDS) and have used them in production. Now we are investigating this operator and wondering how to "import" existing AWS resources with this operator (similar to the import command in Terraform CLI). The reason for it would be that we do not want to have two different tools/operators managing the same kind of resource (RDS databases in this case).
Potential Terraform Configuration
N/A
References
N/A
The text was updated successfully, but these errors were encountered:
Community Note
Description
We have created our own operators (e.g for AWS RDS) and have used them in production. Now we are investigating this operator and wondering how to "import" existing AWS resources with this operator (similar to the
import
command in Terraform CLI). The reason for it would be that we do not want to have two different tools/operators managing the same kind of resource (RDS databases in this case).Potential Terraform Configuration
N/A
References
N/A
The text was updated successfully, but these errors were encountered: