Implement Sensitive Files Check and Health Check Script in CI

[shivasankaran18]

Increasing Access

Unsure

Feature request details

We need to enhance our CI pipeline by adding checks for sensitive files and a health check script to ensure deployment stability

Implement a CI step to check for unauthorized changes to sensitive files during pull requests and a health check script that verifies the application is running correctly on the specified port.

[welcome]

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.

[shivasankaran18]

@raclim can I work on this issue.. ?

[ishwarthecodddr]

@raclim i am working on this issue

[raclim]

Thanks for opening this! @shivasankaran18 and @ishwarthecodddr i think it’s best maybe to talk through some of the changes you’re hoping to implement first before working on it! Could you maybe provide a few more details?

[ishwarthecodddr]

@raclim Developers might accidentally commit actual credentials, API keys, or passwords to the repository. Without proper monitoring, these secrets could be exposed publicly. Adding sensitive files to the CI checks could prevent this .

[shivasankaran18]

@raclim
Check for unauthorized changes to sensitive files during pull requests:
1.dentify which files are considered sensitive.
2. Implement a CI step to check for any changes to these files.
3. Ensure that if unauthorized changes are detected, the CI pipeline fails the pull request.

Health check script to ensure deployment stability:

1. Create a script that verifies the application is running correctly.

If it's all good , I can work on this issue with you approval

[shivasankaran18]

@raclim any comments ..? Can I work on this issue

[raclim]

Thanks so much for your suggestions!

While we do have files that could contain sensitive information (such as .env), they are either meant to be ignored by using .gitignore or hold placeholder information—the actual secrets and credentials are not held within this repository.

Given that, I feel like a CI check for unauthorized changes to these values are not needed right now, and could make it more difficult when we do need to update these files. We also have health checks that are handled by the platforms that we currently use to host the editor, so I don't think we may need a supplementary one here.

I appreciate you taking the time to raise and think about this issue and how to implement security and robustness within the editor! Due to some of the reasons I outlined above, I'm going to close this for now, but I think this is something we could revisit if the scale/infrastructure of the project expands down the line!

[shivasankaran18]

ok @raclim .. thanks for your review