Fix vulnerability issue on docs dependency #1313
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dosubot
bot
added
the
size:XS
dosubot
bot
added
the
area:dependencies
Deploying astronomer-cosmos with
|
| Latest commit: |
4b490c4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3456946d.astronomer-cosmos.pages.dev |
| Branch Preview URL: | https://vulnerability-8.astronomer-cosmos.pages.dev |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1313 +/- ##
=======================================
Coverage 95.85% 95.85%
=======================================
Files 67 67
Lines 3983 3983
=======================================
Hits 3818 3818
Misses 165 165 ☔ View full report in Codecov by Sentry. |
pankajkoti
reviewed
Nov 12, 2024
tatiana
commented
Nov 12, 2024
pankajkoti
approved these changes
Nov 12, 2024
pankajkoti
added a commit
that referenced
this pull request
Nov 13, 2024
It appears we have a flaky Kubernetes test that failed in PR #1313. As shown in the error log [here](https://github.com/astronomer/astronomer-cosmos/actions/runs/11796817624/job/32867560902?pr=1313#step:7:473), the PostgreSQL pod did not reach the ready state and instead entered an error status. Since the cause of the error status is unclear, this PR introduces a status check for the PostgreSQL pod to ensure it becomes fully running and healthy. If the pod enters an ERROR state, we now run a `kubectl describe` command on the pod to capture the event logs for debugging. The test will also exit with an error code of 1 to prevent further execution. related: #1319
https://github.com/astronomer/astronomer-cosmos/security/dependabot/8 Airflow versions before 2.10.3 have a vulnerability that allows authenticated users with audit log access to see sensitive values in audit logs which they should not see. When sensitive variables were set via airflow CLI, values of those variables appeared in the audit log and were stored unencrypted in the Airflow database. While this risk is limited to users with audit log access, it is recommended to upgrade to Airflow 2.10.3 or a later version, which addresses this issue. Users who previously used the CLI to set secret variables should manually delete entries with those variables from the log table.
pankajkoti
force-pushed
the
vulnerability-8
branch
from
eb9ac8a
to
4b490c4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: https://github.com/astronomer/astronomer-cosmos/security/dependabot/8
More details about the vulnerability: