Prevent adding architecture diagrams in Repo - Bit Bucket Cloud

[Sanam Malleswari]

Hi,

Please anyone help on the below requirement best practices. Which will not be override by developer.

• As a administrator, when I manage repositories, I want to prevent the upload of architecture diagrams so that sensitive information is not stored in code repositories.

• As a developer, when I work on code, I want to ensure that design documentation is separate from code assets so that I can maintain clarity and organization.

This issue aims to implement policies in Bitbucket Cloud repositories. The goal is to prevent the upload and storage of architecture diagrams, which can contain sensitive information.

• Policies must be established to block the upload of architecture diagrams.

• Controls should be in place to enforce separation between code assets and design documentation.

• The system should prevent repository bloat caused by large diagram files.

• Architectural diagrams must be stored in appropriate documentation systems.

Other information

• Purpose of the implementation includes maintaining security and enforcing separation of concerns.

[Aron Gombas _Midori_]

How do you identify an "architecture diagram"? Is it a file of a special file type (like SVG)? Or by name? Or how?

I think it is important to answer this first.