Closed mykolalosev closed 4 months ago
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
Moving 10 resources in the
datasync
group:aws_datasync_agent
aws_datasync_location_efs
aws_datasync_location_fsx_lustre_file_system
aws_datasync_location_fsx_openzfs_file_system
aws_datasync_location_fsx_windows_file_system
aws_datasync_location_hdfs
aws_datasync_location_nfs
aws_datasync_location_s3
aws_datasync_location_smb
aws_datasync_task
Details
:aws_datasync_agent
While testing the resource encountered blockers:
Unclear "Deploy your agent as an Amazon EC2 instance" process, need to investigate it more clearly. Need to know what is agent instance - to create an agent on the create agent page we need to put an activation key or agent address.
During creation an agent on the create agent page, after configuring and applying all required resources, we can see them on the resources page - we can't apply some of them: Subnet, Security Group. At first we should: go to the manage page by clicking manage button -> select required resource -> click manage. After that we can select these resources on the create agent page.
This can lead to additional manual interventions and the inability to run automated tests.
agent.log agent.txt
aws_datasync_location_efs
While testing the resource encountered blockers:
This can lead to additional manual interventions and the inability to run automated tests.
locationefs.log locationefs.txt