Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the secrets of the HfLA website repo #3228

Open
1 of 7 tasks
SAUMILDHANKAR opened this issue Jun 7, 2022 · 3 comments
Open
1 of 7 tasks

Document the secrets of the HfLA website repo #3228

SAUMILDHANKAR opened this issue Jun 7, 2022 · 3 comments
Labels
Complexity: Large documentation Documentation creation Feature: Infrastructure For changes on site technical architecture role: back end/devOps Tasks for back-end developers role: dev leads Tasks for technical leads size: 2pt Can be done in 7-12 hours
Milestone

Comments

@SAUMILDHANKAR
Copy link
Member

SAUMILDHANKAR commented Jun 7, 2022

Dependency

Overview

We need to document where the project's secrets are being used, how to access and update them, so that we can use this info in another issue.

Details

We are going to create a GHA generated issue to tell us to update secrets on the repo on biannually. In order for the person to work the issue, they will need to know the information that this issue will provide.

Action Items

  • Read through the suggestions and recommendations from Create a wiki page about best practices for maintaining GitHub secrets #3290
  • Create a spreadsheet to document all the secrets being used in our repo here as well as those which are part of Wins Form Admin Guide, elizabethhonest and HackforLABot accounts. Add information about their functionalities too.
    • This spreadsheet should stay in the HfLA website admin drive.
    • Review and update the permission levels for this spreadsheet if required.
  • Add information for any org level secrets that might have an impact on our repo and need to be maintained by the website team.
  • Since there won't be a PR created for this issue, demo your results to co-leads and PMs in the Dev/PM meeting and close this issue after approval.

Resources/Instructions

@SAUMILDHANKAR SAUMILDHANKAR added documentation Documentation creation role: back end/devOps Tasks for back-end developers Complexity: Large Feature: Infrastructure For changes on site technical architecture size: 2pt Can be done in 7-12 hours labels Jun 7, 2022
@github-actions

This comment was marked as resolved.

@SAUMILDHANKAR SAUMILDHANKAR added the role: dev leads Tasks for technical leads label Jun 7, 2022
@SAUMILDHANKAR SAUMILDHANKAR changed the title Explore and document best practices for resetting secrets in our repo Documenting best practices for resetting secrets Jun 9, 2022
@SAUMILDHANKAR

This comment was marked as off-topic.

@SAUMILDHANKAR SAUMILDHANKAR changed the title Documenting best practices for resetting secrets Document best practices of resetting secrets for website repo Jun 22, 2022
@SAUMILDHANKAR SAUMILDHANKAR added Dependency An issue is blocking the completion or starting of another issue Ready for Prioritization labels Jun 22, 2022
@SAUMILDHANKAR SAUMILDHANKAR changed the title Document best practices of resetting secrets for website repo Document best practices of resetting secrets for HfLA website repo Jun 27, 2022
@7kram

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty changed the title Document best practices of resetting secrets for HfLA website repo Document the secrets of the HfLA website repo Oct 1, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Ready for Prioritization and removed Dependency An issue is blocking the completion or starting of another issue labels Oct 1, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Ice box to New Issue Approval in P: HfLA Website: Project Board Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large documentation Documentation creation Feature: Infrastructure For changes on site technical architecture role: back end/devOps Tasks for back-end developers role: dev leads Tasks for technical leads size: 2pt Can be done in 7-12 hours
Projects
Status: Prioritized backlog
Development

No branches or pull requests

3 participants