Skip to content

Fix for regression deploying resources with PyPi and Maven library types - #2341

Merged
andrewnester merged 1 commit into
mainfrom
fix/using-pypi-library
Feb 12, 2025
Merged

Fix for regression deploying resources with PyPi and Maven library types#2341
andrewnester merged 1 commit into
mainfrom
fix/using-pypi-library

Conversation

@andrewnester

@andrewnesterandrewnester commented Feb 12, 2025

Copy link
Copy Markdown
Contributor

Changes

The CheckForSameNameLibraries mutator incorrectly assumed all resource libraries define libraries as paths of the string type, but some libraries, such as PyPi and Maven, define them as objects.

This PR addresses this issue. It was introduced in #2297.

Tests

Added regression test.

@andrewnester
andrewnester merged commit ac439f8 into mainFeb 12, 2025
@andrewnester
andrewnester deleted the fix/using-pypi-library branch February 12, 2025 16:14
andrewnester added a commit that referenced this pull request Feb 12, 2025
Bundles:
* Fix for regression deploying resources with PyPi and Maven library types ([#2341](#2341)).
andrewnester added a commit that referenced this pull request Feb 12, 2025
Bundles:
* Fix for regression deploying resources with PyPi and Maven library
types ([#2341](#2341)).
pietern added a commit that referenced this pull request Feb 12, 2025
pietern added a commit that referenced this pull request Feb 12, 2025
## Changes
These changes break the use of non-local libraries (such as PyPI
libraries).
This reverts the set so we can cut a patch release and take a closer
look later.
Original PRs are #2297 and #2341.
Issue reported in #2343.
## Tests
Manually confirmed that a bundle with PyPI package in libraries now
deploys fine.
github-merge-queueBot pushed a commit that referenced this pull request Feb 27, 2025
…basename used (#2382)
## Changes
It could happen that there are multiple artifacts defined in the bundle
which build and therefore deploy wheel packages with the same name. This
leads to conflict between these packages, they will overwrite each other
and therefore they should have different names instead
Fixes#1674
Previous attempt (#2297 +
#2341) led to the breakage, this
PR fixes both issues.
## Tests
Added acceptance test
HariGS-DB pushed a commit to HariGS-DB/cli that referenced this pull request Feb 28, 2025
…basename used (databricks#2382)
## Changes
It could happen that there are multiple artifacts defined in the bundle
which build and therefore deploy wheel packages with the same name. This
leads to conflict between these packages, they will overwrite each other
and therefore they should have different names instead
Fixesdatabricks#1674
Previous attempt (databricks#2297 +
databricks#2341) led to the breakage, this
PR fixes both issues.
## Tests
Added acceptance test
denik pushed a commit that referenced this pull request May 20, 2026
…pes (#2341)
## Changes
The CheckForSameNameLibraries mutator incorrectly assumed all resource
libraries define libraries as paths of the `string` type, but some
libraries, such as PyPi and Maven, define them as objects.
This PR addresses this issue. It was introduced in #2297.
## Tests
Added regression test.
denik pushed a commit that referenced this pull request May 20, 2026
Bundles:
* Fix for regression deploying resources with PyPi and Maven library
types ([#2341](#2341)).
denik pushed a commit that referenced this pull request May 20, 2026
## Changes
These changes break the use of non-local libraries (such as PyPI
libraries).
This reverts the set so we can cut a patch release and take a closer
look later.
Original PRs are #2297 and #2341.
Issue reported in #2343.
## Tests
Manually confirmed that a bundle with PyPI package in libraries now
deploys fine.
denik pushed a commit that referenced this pull request May 20, 2026
…basename used (#2382)
## Changes
It could happen that there are multiple artifacts defined in the bundle
which build and therefore deploy wheel packages with the same name. This
leads to conflict between these packages, they will overwrite each other
and therefore they should have different names instead
Fixes#1674
Previous attempt (#2297 +
#2341) led to the breakage, this
PR fixes both issues.
## Tests
Added acceptance test
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@andrewnester@pietern