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

Mark Release available with connection details #82

Merged
merged 1 commit into from
Mar 25, 2021

Conversation

srueg
Copy link
Contributor

@srueg srueg commented Mar 25, 2021

Description of your changes

Only mark a release as available once all connection details are ready.

Fixes #81

I have:

  • Read and followed Crossplane's contribution process.
  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Tested on cluster. Both with a Release containing connectionDetails and one without any.

Only mark a release as available once all connection details are ready.

Fixes crossplane-contrib#81

Signed-off-by: Simon Rüegg <simon@rueggs.ch>
@srueg
Copy link
Contributor Author

srueg commented Mar 25, 2021

@turkenh let me know what you think of this. I'll run some local tests to see if it actually solves the issue mentioned in #81 .

@turkenh
Copy link
Collaborator

turkenh commented Mar 25, 2021

@srueg, this looks good to me.
Please also test without connection details.

@srueg
Copy link
Contributor Author

srueg commented Mar 25, 2021

I did some tests both including connectionDetails and some without. Looking good 👍

Copy link
Collaborator

@turkenh turkenh left a comment

Choose a reason for hiding this comment

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

Thanks!

@turkenh turkenh merged commit e474064 into crossplane-contrib:master Mar 25, 2021
@srueg srueg deleted the connection-details-ready branch March 25, 2021 16:29
@srueg
Copy link
Contributor Author

srueg commented Mar 29, 2021

@turkenh should we release a patch version (v0.5.1) with this? Or just cut v0.6.0?

@turkenh
Copy link
Collaborator

turkenh commented Mar 31, 2021

@turkenh should we release a patch version (v0.5.1) with this? Or just cut v0.6.0?

@srueg just released v0.6.0

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.

Release in Ready state before connection details are available
2 participants