Getting repository ruleset bypass actors shouldn't require write access to that ruleset

[calvis]

Select Topic Area

Product Feedback

Body

https://docs.github.com/en/rest/repos/rules?apiVersion=2022-11-28#get-a-repository-ruleset

Get a ruleset for a repository.
Note: To prevent leaking sensitive information, the bypass_actors property is only returned if the user making the API request has write access to the ruleset.

I have a terraform plan credentials (from a GitHub app) that has Administration (read-only) privilege in a repository. It cannot get the bypass_actors because it does not have write access to the ruleset, which causes permanent drift where terraform constantly tries to add the bypass_actors onto the ruleset that already has them:

      + bypass_actors {
          + actor_id    = 2
          + actor_type  = "RepositoryRole"
          + bypass_mode = "always"
        }

The GET ruleset API should return the bypass_actors when the token has Administration (read-only) permissions. "Leaking sensitive information" about a ruleset is not a security concern when the user is an administrator. Otherwise, I simply can't manage rulesets with terraform due to the volume of noise this would create, as it is a security concern to give the app write permissions or switch to a classic token.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐