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

implement secret scanning or some block for edited studio-args.txt files to prevent developers accidentally committing secrets to VCS #1

Closed
tallguyjenks opened this issue Jul 9, 2024 · 1 comment
Assignees
Labels
feature Additions to functionality security Security Issues or requirements

Comments

@tallguyjenks
Copy link
Member

No description provided.

@tallguyjenks tallguyjenks added enhancement Improvement of existing features and functionality dev feature Additions to functionality security Security Issues or requirements and removed enhancement Improvement of existing features and functionality dev labels Jul 15, 2024
@tallguyjenks
Copy link
Member Author

resolved via workflow change, dont modify the studio file except to add new line items for variables needed to spin up application and secrets only get placed into the vm args screen for the application after pasting the contents of studio-args.txt into that interface for modification.

@tallguyjenks tallguyjenks self-assigned this Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Additions to functionality security Security Issues or requirements
Projects
None yet
Development

No branches or pull requests

1 participant