Authentication for IAC #152505
Replies: 1 comment
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
I am encountering a persistent issue while attempting to manage our GitHub Enterprise Cloud environment using Infrastructure as Code (IaC).
The challenge arises when creating and configuring organizations. The initial creation of an organization (e.g., setting the name, billing email, etc.) does not require the token to be authorized against the organization, as it does not yet exist. However, applying additional settings afterward does require authorization. This disrupts the IaC workflow, preventing a seamless, end-to-end process for organization creation and management.
I understand the security concerns around granting a token enterprise-wide administrative rights. However, the lack of an alternative with sufficient permissions creates a significant limitation in managing our environment efficiently.
I would appreciate any thoughts, potential solutions, or guidance on how to address this challenge.
Beta Was this translation helpful? Give feedback.
All reactions