Skip to content

Conversation

Harsh4902
Copy link

Description

  • This PR fixes MicrocksClient, which was not able to handle insecure TLS request previously.

Related issue(s)

Fixes #180

Copy link

github-actions bot commented Sep 7, 2025

This pull request has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale State due to inactivity label Sep 7, 2025
@lbroudoux lbroudoux added kind/bug Something isn't working component/cli and removed stale State due to inactivity labels Sep 8, 2025
@lbroudoux lbroudoux added this to the 1.0.0 milestone Sep 8, 2025
Copy link
Member

@lbroudoux lbroudoux left a comment

Choose a reason for hiding this comment

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

It embeds commits from previous PR like #160 but seems safe to merge after a rebase. I can't do it with the GitiHub UI: some prerequisites are failing. @Harsh4902 can you do this easily?

@Harsh4902
Copy link
Author

It embeds commits from previous PR like #160 but seems safe to merge after a rebase. I can't do it with the GitiHub UI: some prerequisites are failing. @Harsh4902 can you do this easily?

Okay, I'll take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/cli kind/bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants