You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm loading the S3 settings via a volumes.php config with references to ENV variables form the .ENV file. When adding this S3 asset source to Craft 3.1 the AWS credentials are being stored in the project.yaml file. This also puts them into version control and is a potential security issue.
I know this is related to issue #35, but is there a way to prevent them from being added to the yaml?
The text was updated successfully, but these errors were encountered:
I'm loading the S3 settings via a volumes.php config with references to ENV variables form the .ENV file. When adding this S3 asset source to Craft 3.1 the AWS credentials are being stored in the project.yaml file. This also puts them into version control and is a potential security issue.
I know this is related to issue #35, but is there a way to prevent them from being added to the yaml?
The text was updated successfully, but these errors were encountered: