Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

423 remove service discovery #425

Merged
merged 2 commits into from
Oct 21, 2024
Merged

Conversation

jacksondelametter
Copy link
Contributor

@jacksondelametter jacksondelametter commented Oct 18, 2024

PR to remove the Service Discovery module. This also adds to the Draft Release Notes that the module has been removed as well as fix a commit hash reference to the removal of Sagemaker.

@@ -101,4 +101,5 @@ If you added any custom configurations to the `sparkoperator` service account pe

# What's Changed
- `pyproject.toml` files updated to allow for Python version `>=3.8`.
- All SageMaker modules and corresponding references were removed in commit bdcbb409.
- All SageMaker modules and corresponding references were removed in commit 8ce3f39.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- All SageMaker modules and corresponding references were removed in commit 8ce3f39.
- All SageMaker modules and corresponding references were removed in commit 8ce393f.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@@ -101,4 +101,5 @@ If you added any custom configurations to the `sparkoperator` service account pe

# What's Changed
- `pyproject.toml` files updated to allow for Python version `>=3.8`.
- All SageMaker modules and corresponding references were removed in commit bdcbb409.
- All SageMaker modules and corresponding references were removed in commit 8ce3f39.
- The Service Discovery module and corresponding references were removed in commit 4a1d7abf.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You currently have 2 commits, so this is probably gonna change if you squash them

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately I need to have two commits to do this. When you squash them, git changes the commit hash.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh that makes sense, can't predict the squash commit hash

@jacksondelametter jacksondelametter merged commit d31f536 into dev Oct 21, 2024
@jacksondelametter jacksondelametter deleted the 423-remove-service-discovery branch October 21, 2024 13:40
Sign up for free to 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