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

[DPE-5015] Fix integration hub not parsing equals sign properly #6

Merged
merged 2 commits into from
Aug 2, 2024

Conversation

theoctober19th
Copy link
Member

No description provided.

Copy link
Contributor

@deusebio deusebio left a comment

Choose a reason for hiding this comment

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

Could we maybe have a small tests with the use case of the double equals?

@deusebio
Copy link
Contributor

deusebio commented Aug 2, 2024

Oki! Just realized that we don't have tests here. Let's then skip the tests here, but it would be good to have that tests in the integration hub.

It should be pretty easy, we set the charm to populate a config with double equals, and we make sure that we can fetch that

@deusebio deusebio self-requested a review August 2, 2024 12:38
@theoctober19th
Copy link
Member Author

theoctober19th commented Aug 2, 2024

@deusebio I have those tests in the Operator. Since there are no tests here, adding them from scratch felt more like a separate task with wider scope.

Here is the PR: canonical/spark-integration-hub-k8s-operator#18

@deusebio
Copy link
Contributor

deusebio commented Aug 2, 2024

@deusebio yes yes, I noticed and I have revised my comment above and approved.

We are on the same page, as you have already implemented the tests in the operator! Thanks!

@theoctober19th theoctober19th merged commit e671219 into 3.4-22.04/edge Aug 2, 2024
2 checks passed
@theoctober19th theoctober19th deleted the fix-double-equals branch August 2, 2024 12:45
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