eea.plotly 2.4__tar.gz → 2.5__tar.gz

{eea_plotly-2.4/eea.plotly.egg-info → eea_plotly-2.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: eea.plotly
-Version: 2.4
+Version: 2.5
 Summary: volto-plotlycharts backend support
 Home-page: https://github.com/eea/eea.plotly
 Author: European Environment Agency: IDM2 A-Team
@@ -143,9 +143,64 @@ EEA_ - European Environment Agency (EU)
 .. _EEA: https://www.eea.europa.eu/
 .. _`EEA Web Systems Training`: http://www.youtube.com/user/eeacms/videos?view=1
 
+Secret Scanning
+===============
+
+This repository uses the Betterleaks GitHub Action to scan the current
+repository content on every push and pull request. The scan uses the rules in
+``.gitleaks.toml`` and uploads a ``betterleaks-report`` artifact when a finding
+is detected.
+
+If the optional SMTP secrets are configured, failed scans also send an email to
+the last commit committer. The workflow expects these repository or
+organization secrets:
+
+- ``SMTP_URL``
+- ``SMTP_PORT`` (optional, defaults to ``25``)
+- ``SMTP_EMAIL``
+- ``SMTP_PASSWORD`` (optional if the SMTP server does not require authentication)
+
+Port ``465`` is sent with direct TLS; other ports use the default SMTP
+handshake. The email includes a short finding summary from the redacted
+Betterleaks report, including the redacted matched line from each finding.
+
+There are three common outcomes:
+
+1. Everything is OK. The ``Betterleaks / Scan for secrets`` check is green and
+   no action is needed. Regular references to runtime values are OK, for example::
+
+     token_from_cookie = request.cookies.get("auth_token")
+
+2. A real secret was found. The check is red and the workflow log asks you to
+   download the ``betterleaks-report`` artifact. Open the artifact from the
+   GitHub Actions run and check the reported file, line and rule. Remove the
+   committed value, move it to the proper secret store, and rotate it if it was
+   exposed. A report entry looks like this::
+
+     {
+       "RuleID": "secret-literal-assignment",
+       "File": "src/config.py",
+       "StartLine": 12,
+       "Secret": "[REDACTED]"
+     }
+
+3. The finding is a false positive. Keep the value only if it is clearly not
+   sensitive, such as a test fixture, placeholder, or public example. Add
+   ``betterleaks:allow`` on the same line and include a short explanation in the
+   pull request::
+
+     test_password = "admin"  #betterleaks:allow
+
+Do not add ``betterleaks:allow`` to real credentials.
+
 Changelog
 =========
 
+2.5 - (2026-07-13)
+---------------------------
+* Change: fix: SonarQube report - refs #305404
+  [avoinea]
+
 2.4 - (2026-05-26)
 ---------------------------
 * Change: Implement eea.genai.summary customization

{eea_plotly-2.4 → eea_plotly-2.5}/README.rst

@@ -101,3 +101,53 @@ EEA_ - European Environment Agency (EU)
 
 .. _EEA: https://www.eea.europa.eu/
 .. _`EEA Web Systems Training`: http://www.youtube.com/user/eeacms/videos?view=1
+
+Secret Scanning
+===============
+
+This repository uses the Betterleaks GitHub Action to scan the current
+repository content on every push and pull request. The scan uses the rules in
+``.gitleaks.toml`` and uploads a ``betterleaks-report`` artifact when a finding
+is detected.
+
+If the optional SMTP secrets are configured, failed scans also send an email to
+the last commit committer. The workflow expects these repository or
+organization secrets:
+
+- ``SMTP_URL``
+- ``SMTP_PORT`` (optional, defaults to ``25``)
+- ``SMTP_EMAIL``
+- ``SMTP_PASSWORD`` (optional if the SMTP server does not require authentication)
+
+Port ``465`` is sent with direct TLS; other ports use the default SMTP
+handshake. The email includes a short finding summary from the redacted
+Betterleaks report, including the redacted matched line from each finding.
+
+There are three common outcomes:
+
+1. Everything is OK. The ``Betterleaks / Scan for secrets`` check is green and
+   no action is needed. Regular references to runtime values are OK, for example::
+
+     token_from_cookie = request.cookies.get("auth_token")
+
+2. A real secret was found. The check is red and the workflow log asks you to
+   download the ``betterleaks-report`` artifact. Open the artifact from the
+   GitHub Actions run and check the reported file, line and rule. Remove the
+   committed value, move it to the proper secret store, and rotate it if it was
+   exposed. A report entry looks like this::
+
+     {
+       "RuleID": "secret-literal-assignment",
+       "File": "src/config.py",
+       "StartLine": 12,
+       "Secret": "[REDACTED]"
+     }
+
+3. The finding is a false positive. Keep the value only if it is clearly not
+   sensitive, such as a test fixture, placeholder, or public example. Add
+   ``betterleaks:allow`` on the same line and include a short explanation in the
+   pull request::
+
+     test_password = "admin"  #betterleaks:allow
+
+Do not add ``betterleaks:allow`` to real credentials.

{eea_plotly-2.4 → eea_plotly-2.5}/docs/HISTORY.txt

@@ -1,6 +1,11 @@
 Changelog
 =========
 
+2.5 - (2026-07-13)
+---------------------------
+* Change: fix: SonarQube report - refs #305404
+  [avoinea]
+
 2.4 - (2026-05-26)
 ---------------------------
 * Change: Implement eea.genai.summary customization

eea_plotly-2.5/eea/plotly/version.txt

@@ -0,0 +1 @@
+2.5

{eea_plotly-2.4 → eea_plotly-2.5/eea.plotly.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: eea.plotly
-Version: 2.4
+Version: 2.5
 Summary: volto-plotlycharts backend support
 Home-page: https://github.com/eea/eea.plotly
 Author: European Environment Agency: IDM2 A-Team
@@ -143,9 +143,64 @@ EEA_ - European Environment Agency (EU)
 .. _EEA: https://www.eea.europa.eu/
 .. _`EEA Web Systems Training`: http://www.youtube.com/user/eeacms/videos?view=1
 
+Secret Scanning
+===============
+
+This repository uses the Betterleaks GitHub Action to scan the current
+repository content on every push and pull request. The scan uses the rules in
+``.gitleaks.toml`` and uploads a ``betterleaks-report`` artifact when a finding
+is detected.
+
+If the optional SMTP secrets are configured, failed scans also send an email to
+the last commit committer. The workflow expects these repository or
+organization secrets:
+
+- ``SMTP_URL``
+- ``SMTP_PORT`` (optional, defaults to ``25``)
+- ``SMTP_EMAIL``
+- ``SMTP_PASSWORD`` (optional if the SMTP server does not require authentication)
+
+Port ``465`` is sent with direct TLS; other ports use the default SMTP
+handshake. The email includes a short finding summary from the redacted
+Betterleaks report, including the redacted matched line from each finding.
+
+There are three common outcomes:
+
+1. Everything is OK. The ``Betterleaks / Scan for secrets`` check is green and
+   no action is needed. Regular references to runtime values are OK, for example::
+
+     token_from_cookie = request.cookies.get("auth_token")
+
+2. A real secret was found. The check is red and the workflow log asks you to
+   download the ``betterleaks-report`` artifact. Open the artifact from the
+   GitHub Actions run and check the reported file, line and rule. Remove the
+   committed value, move it to the proper secret store, and rotate it if it was
+   exposed. A report entry looks like this::
+
+     {
+       "RuleID": "secret-literal-assignment",
+       "File": "src/config.py",
+       "StartLine": 12,
+       "Secret": "[REDACTED]"
+     }
+
+3. The finding is a false positive. Keep the value only if it is clearly not
+   sensitive, such as a test fixture, placeholder, or public example. Add
+   ``betterleaks:allow`` on the same line and include a short explanation in the
+   pull request::
+
+     test_password = "admin"  #betterleaks:allow
+
+Do not add ``betterleaks:allow`` to real credentials.
+
 Changelog
 =========
 
+2.5 - (2026-07-13)
+---------------------------
+* Change: fix: SonarQube report - refs #305404
+  [avoinea]
+
 2.4 - (2026-05-26)
 ---------------------------
 * Change: Implement eea.genai.summary customization

{eea_plotly-2.4 → eea_plotly-2.5}/eea.plotly.egg-info/SOURCES.txt

@@ -141,8 +141,6 @@ eea/plotly/serializer/configure.zcml
 eea/plotly/serializer/dxfields.py
 eea/plotly/serializer/utils.py
 eea/plotly/tests/__init__.py
-eea/plotly/tests/base.py
-eea/plotly/tests/test_doctests.py
 eea/plotly/tests/test_leak_prevention.py
 eea/plotly/tests/test_utils.py
 eea/plotly/upgrades/__init__.py

eea_plotly-2.4/eea/plotly/tests/base.py

@@ -1,51 +0,0 @@
-"""Base test cases"""
-
-from Products.CMFPlone import setuphandlers
-from plone.testing import z2
-from plone.app.testing import TEST_USER_ID
-from plone.app.testing import PloneSandboxLayer
-from plone.app.testing import applyProfile
-from plone.app.testing import FunctionalTesting
-from plone.app.testing import setRoles
-from plone.testing.zope import installProduct
-
-
-class EEAFixture(PloneSandboxLayer):
-    """EEA Testing Policy"""
-
-    def setUpZope(self, app, configurationContext):
-        """Setup Zope"""
-        import eea.plotly
-
-        self.loadZCML(package=eea.plotly)
-
-        installProduct(app, "eea.plotly")
-
-    def setUpPloneSite(self, portal):
-        """Setup Plone"""
-        applyProfile(portal, "eea.plotly:default")
-
-        # Default workflow
-        wftool = portal["portal_workflow"]
-        wftool.setDefaultChain("simple_publication_workflow")
-
-        # Login as manager
-        setRoles(portal, TEST_USER_ID, ["Manager"])
-
-        # Add default Plone content
-        try:
-            applyProfile(portal, "plone.app.contenttypes:plone-content")
-        except KeyError:
-            # BBB Plone 4
-            setuphandlers.setupPortalContent(portal)
-
-        # Create testing environment
-        portal.invokeFactory("Folder", "sandbox", title="Sandbox")
-
-    def tearDownZope(self, app):
-        """Uninstall Zope"""
-        z2.uninstallProduct(app, "eea.plotly")
-
-
-EEAFIXTURE = EEAFixture()
-FUNCTIONAL_TESTING = FunctionalTesting(bases=(EEAFIXTURE,), name="EEAplotly:Functional")

eea_plotly-2.4/eea/plotly/tests/test_doctests.py

@@ -1,31 +0,0 @@
-"""Doc tests"""
-
-import doctest
-import unittest
-from eea.plotly.tests.base import FUNCTIONAL_TESTING
-from plone.testing import layered
-
-OPTIONFLAGS = (
-    doctest.REPORT_ONLY_FIRST_FAILURE | doctest.ELLIPSIS | doctest.NORMALIZE_WHITESPACE
-)
-
-
-def test_suite():
-    """Suite"""
-    suite = unittest.TestSuite()
-    suite.addTests(
-        [
-            layered(
-                doctest.DocFileSuite(
-                    "README.txt", optionflags=OPTIONFLAGS, package="eea.plotly"
-                ),
-                layer=FUNCTIONAL_TESTING,
-            ),
-        ]
-    )
-
-    return suite
-
-
-if __name__ == "__main__":
-    unittest.main(defaultTest="test_suite")

eea_plotly-2.4/eea/plotly/version.txt

@@ -1 +0,0 @@
-2.4