API Endpoint for organization-level secret details has updated "updated_at" key even when no change was made to the organization secret

[ivica3730k]

Select Topic Area

Bug

Body

Hello!

I've noticed that when you go to Actions secrets at the organization level, click on an existing secret, and then click the "Save changes" button without making any changes to the secret value or repository access settings, the updated_at field at https://api.github.com/orgs/(org-name)/actions/secrets/(secret-name) still gets updated.

There has been no secret values/visibility change between these two cURL calls, but yet you can see the value of updated_at key has changed

Where does it become a problem?

I have noticed this behaviour while raising issue with the github terraform provider which can be seen here: integrations/terraform-provider-github#2614

It seems like this provider for example is using the updated_at key to track the resource changes, which prevents the terraform to work properly (see details on the issue above)

I am wondering if this is the expected behaviour (updated_at field being updated even when there is no change to the secret value/visibility). I can imagine other tools out there and not just terraform being affected by this behaviour.

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