Open polocato opened 2 years ago
@polocato Thank you for your attention. I'm sorry that I don't quite understand what you mean. Do you mean to add parameter ’manual-request' or do you want to specify different tenants ? Thank you very much!
Hello, thank you for looking into my request. I'd like to ask for manual-request parameter, from my perspective this is not a missing feature but a some kind of bug/missing core functionality. Without that parameter you can't create a private link between two unrelated companies. Best Regards
@polocato Thank you for your reply, but I have checked the latest API and found that 'manual-request' is not supported and cannot be added for the time being. Once it is supported, we will add it as soon as possible. Thank you very much!
I believe this is covered by the manual_private_link_service_connections
field in the PrivateEndpoint object here:
https://learn.microsoft.com/en-us/python/api/azure-mgmt-network/azure.mgmt.network.models.privateendpoint?view=azure-python
(Just ran into the same requirement)
SUMMARY
Private endpoint creation is failing when tenant is not authorized to access linked subscription az cli has an option: --manual-request true
ISSUE TYPE
COMPONENT NAME
azure_rm_privateendpoin
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
WSL1 with ubuntu18.04
STEPS TO REPRODUCE
Setup prive endpoint when tenant is not authorized to access linked subscription ( e.g. different company)
EXPECTED RESULTS
Private endpoint gets created
ACTUAL RESULTS
Playbook fails because it cant modify resources in the subscription