CLOUDP-315273: Onboard Papertrail

[cveticm]

Proposed changes

Sets up new step in release process to lodge metadata in Papertrail for each release.
The metadata is made up of:

• release version
• filenames of each package

Product names are:

• atlascli - for stable releases
• atlascli-snapshot - for unstable releases
• atlascli-test - for testing

See here for test Papertrail run: https://papertrail.prod.corp.mongodb.com/product-version?product=atlascli-test&version=1.42.2
Associated patch: https://spruce.mongodb.com/task/mongodb_atlas_cli_master_test_papertrail_papertrail_test_patch_7d2dbe767468643cb196297868a7d1e9999bcbbc_682ca4ec0ef6fc00071ecdb4_25_05_20_15_51_15/logs?execution=0&logtype=all
Note: You will notice that the only file for each papertrail entry in atlascli-test version 1.42.2 is .keep. This was the test file used for testing.

Jira ticket: CLOUDP-315273

Checklist

• I have signed the MongoDB CLA
• I have added tests that prove my fix is effective or that my feature works
• I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
• I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
• I have updated test/README.md (if an e2e test has been added)
• I have run make fmt and formatted my code

[blva]

Suggested change

	if [[ "${unstable}" == "-unstable" ]]; then
	if [[ "${unstable:-}" == "-unstable" ]]; then

avoid issues if the value is not set

[blva]

do we need

maybe

        include_expansions_in_env:
          - unstable
``

[cveticm]

Sure! I see in the EVG docs that include_expansions_in_env has greater priority than env so happy to do the change.

Is this the reason for this suggestion or is there another reason to do one over the other?

[andreaangiolillo]

Looking at https://github.com/10gen/release-infrastructure-papertrail?tab=readme-ov-file#required-metadata:
I see that there are a few different metadata fields to include that are missing here. Do you plan to add them later or we don't need them? Also they use product instead of product_name

[cveticm]

The Evergreen task papertrail.trace only takes:

• work_dir
• key_id
• secret_key
• product
• version
• filename

Evergreen then takes care of the remaining fields as, in the test Papertrail stamp, we see information like submitter and sha256 are included.

Also, use of product_name instead of product for the env var was arbitrary. Will change it to product for clarity.

[github-actions]

Coverage Report 📈

Branch	Commit	Coverage
master	7d2dbe7	25.1%
CLOUDP-315273_onboard_papertrail	3861e1f	25.1%
	Difference	0%