Update README.md with details on final report names and user access p…

…ermissions (#300)
liquibase · Jan 30, 2025 · 9c7ecca · 9c7ecca
1 parent e6ee56f
commit 9c7ecca
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -468,4 +468,12 @@ When you want to release new version of `build-logic`, it is important to update
    - the individual reports are uploaded under `raw_reports`
    - the combined reports is called `enterprise_report_version_number_for_report_generation` which is uploaded under `version_number_for_report_generation` 
    - the report for `datical-service` is uploaded under version_number_for_report_generation
-4. You might need to do some manipulation of the columns as sometimes they are empty. Just the way Fossa populates them! 
+4. You might need to do some manipulation of the columns as sometimes they are empty. Just the way Fossa populates them! 
+5. Final combined report for all repos except datical-service is called `enterprise_report_8.7.352.csv`
+6. Final separate report for datical-service is called `datical-service.csv`
+
+![](./doc/img/aws-s3-bucket-enterprise-reports.png)
+
+7. If we plan on sending this report to the users it will be on some page like we have for OSS -> https://www.liquibase.com/eula and they will have access to only the URI’s we mention. As to to the liquibase users, DevOps team can add them to permission set to have access to those reports. 
+
+![](./doc/img/permission-set-enterprise-fossa-report.png)
diff --git a/doc/img/aws-s3-bucket-enterprise-reports.png b/doc/img/aws-s3-bucket-enterprise-reports.png
diff --git a/doc/img/permission-set-enterprise-fossa-report.png b/doc/img/permission-set-enterprise-fossa-report.png