Ryan and Mikhail believe that the post access support should be handled by the related sub-project/community, i.e. physical risk. Mikhail suggests these communities nominate a tech owner which can help with documentation related to their specific project needs. edit: Mikhail suggests these users could also act as approvers on the access being granted.
Update the template to define whether this is being used as a service user/application access or as an individual using it to upload/store/read directly from the bucket.
Use the LF Support queue to request these services: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/create/35 this can reference the github project issues, but will help track and prioritize the requests as they come in (and scale across the team/timezones/etc).
Ryan and Mikhail believe that the post access support should be handled by the related sub-project/community, i.e. physical risk. Mikhail suggests these communities nominate a tech owner which can help with documentation related to their specific project needs. edit: Mikhail suggests these users could also act as approvers on the access being granted.
Update the template to define whether this is being used as a service user/application access or as an individual using it to upload/store/read directly from the bucket.