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
Can we get a real list of the permissions needed to use each section of the builder? There seem to be only very old versions of this from when Jetbrains maintained this. While some of those are still applicable, there have been new features added that are not documented permissions wise. Such as publish to content library, I have given the account full content library access and it doesn't work.
The only way I can get it to work is to give it Global Permission Administrator.
I have tried Giving it Global Permission Read-only and all the rest of the normal packer permissions and everything works until it gets to publish to content library then I get a 403 forbidden.
Use Case(s)
To be able to publish a packer created OVA to a local content library in a production environment with out giving the account Global Administrator role in vcenter. An all encompassing permissions list that are needed should be provided.
Potential configuration
VCenter Server 6.7u3
VMware ESXi, 6.7.0, 17499825
Permissions my account has that will preform all operations except publish OVA to content library.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
May 27, 2021
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Can we get a real list of the permissions needed to use each section of the builder? There seem to be only very old versions of this from when Jetbrains maintained this. While some of those are still applicable, there have been new features added that are not documented permissions wise. Such as publish to content library, I have given the account full content library access and it doesn't work.
The only way I can get it to work is to give it Global Permission Administrator.
I have tried Giving it Global Permission Read-only and all the rest of the normal packer permissions and everything works until it gets to publish to content library then I get a 403 forbidden.
Use Case(s)
To be able to publish a packer created OVA to a local content library in a production environment with out giving the account Global Administrator role in vcenter. An all encompassing permissions list that are needed should be provided.
Potential configuration
VCenter Server 6.7u3
VMware ESXi, 6.7.0, 17499825
Permissions my account has that will preform all operations except publish OVA to content library.
Alarms
Content Library
Datastore
Folder
Host
Network
Virtual machine
Potential References
https://www.packer.io/docs/builders/vmware/vsphere-iso
jetbrains-infra/packer-builder-vsphere#97
The text was updated successfully, but these errors were encountered: