Skip to content

Commit 53fff0a

Browse files
committed
Add artifact name to env variable
1 parent 8a7032e commit 53fff0a

File tree

2 files changed

+11
-8
lines changed

2 files changed

+11
-8
lines changed

.github/workflows/release_build.yml

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ env:
1414
RELEASE_PRIVATE_REPOSITORY: 020628701572.dkr.ecr.us-west-2.amazonaws.com/adot-autoinstrumentation-python
1515
RELEASE_PRIVATE_REGISTRY: 020628701572.dkr.ecr.us-west-2.amazonaws.com
1616
PACKAGE_NAME: aws-opentelemetry-distro
17+
ARTIFACT_NAME: aws_opentelemetry_distro-${{ github.event.inputs.version }}-py3-none-any.whl
1718

1819
permissions:
1920
id-token: write
@@ -88,15 +89,15 @@ jobs:
8889
TWINE_USERNAME: '__token__'
8990
TWINE_PASSWORD: ${{ env.TEST_PYPI_TOKEN_API_TOKEN }}
9091
run: |
91-
twine upload --repository testpypi --skip-existing --verbose dist/aws_opentelemetry_distro-${{ github.event.inputs.version }}-py3-none-any.whl
92+
twine upload --repository testpypi --skip-existing --verbose dist/${{ env.ARTIFACT_NAME }}
9293
9394
# Publish to prod PyPI
9495
- name: Publish to PyPI
9596
env:
9697
TWINE_USERNAME: '__token__'
9798
TWINE_PASSWORD: ${{ env.PROD_PYPI_TOKEN_API_TOKEN }}
9899
run: |
99-
twine upload --skip-existing --verbose dist/aws_opentelemetry_distro-${{ github.event.inputs.version }}-py3-none-any.whl
100+
twine upload --skip-existing --verbose dist/${{ env.ARTIFACT_NAME }}
100101
101102
# Publish to public ECR
102103
- name: Build and push public ECR image
@@ -122,11 +123,8 @@ jobs:
122123
123124
- name: Get SHA256 checksum of wheel file
124125
id: get_sha256
125-
env:
126-
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
127126
run: |
128-
filename="aws_opentelemetry_distro-${{ github.event.inputs.version }}-py3-none-any.whl"
129-
shasum -a 256 dist/$filename | awk '{print $1}' > $filename.sha256
127+
shasum -a 256 dist/${{ env.ARTIFACT_NAME }} | sed "s|dist/||" > ${{ env.ARTIFACT_NAME }}.sha256
130128
131129
# Publish to GitHub releases
132130
- name: Create GH release
@@ -138,5 +136,5 @@ jobs:
138136
--title "Release v${{ github.event.inputs.version }}" \
139137
--draft \
140138
"v${{ github.event.inputs.version }}" \
141-
dist/aws_opentelemetry_distro-${{ github.event.inputs.version }}-py3-none-any.whl \
142-
aws_opentelemetry_distro-${{ github.event.inputs.version }}-py3-none-any.whl.sha256
139+
dist/${{ env.ARTIFACT_NAME }} \
140+
${{ env.ARTIFACT_NAME }}.sha256

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,3 +39,8 @@ This project ensures compatibility with the following supported Python versions:
3939

4040
### Note on Amazon CloudWatch Application Signals
4141
[Amazon CloudWatch Application Signals](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.html) components are designed to seamlessly work with all library instrumentations offered by [OpenTelemetry Python auto-instrumentation](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/README.md). While upstream OpenTelemetry Python instrumentations are in beta, Application Signals components are stable, production ready and have also been tested for popular libraries/frameworks such as [Django, Boto3, and others](https://github.com/aws-observability/aws-otel-python-instrumentation/tree/main/contract-tests/images/applications). We will prioritize backward compatibility for Application Signals components, striving to ensure that they remain functional even in the face of potential breaking changes introduced by OpenTelemetry upstream libraries. Please [raise an issue](https://github.com/aws-observability/aws-otel-python-instrumentation/blob/main/CONTRIBUTING.md#reporting-bugsfeature-requests) if you notice Application Signals doesn't work for a particular OpenTelemetry supported library.
42+
43+
## Checksum Verification
44+
Artifacts released will include a `.sha256` file for checksum verification starting from v0.7.0
45+
To verify, run the command `shasum -a 256 -c <artifact_name>.sha256`
46+
It should return the output `<artifact_name>: OK` if the validation is successful

0 commit comments

Comments
 (0)