-
Notifications
You must be signed in to change notification settings - Fork 35
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
Ensure API document is available before returning name #2540
Ensure API document is available before returning name #2540
Conversation
@brylie It is a little fix but I'm afraid that is not a solution of entire problem. Please make sure that removing API document with Proxy connection works as expected (related Proxy Backend is removed as well) Also I think we need to create |
@marla-singer Can I assign you to this PR? |
@bajiat Yes |
Don't merge yet. |
@bajiat should we release this as a 0.43.1 or 0.44.1 patch? If we want to make it available quickly, we discussed that 0.43.1 is better than 0.44.1. Otherwise, if we plan to upgrade customer deployments soon with 0.44.x, then 0.44.1 would be alright. |
@brylie What status of this PR? |
I think at this point we should target the PR for 0.44.1, so we can finish the work. cc: @bajiat |
At this point it should be 44.1 |
@brylie Are you sure that we need to merge it directly to |
@mauriciovieira, @ashakunt, @kumargs: If we merge this branch in to |
@marla-singer I dont know exactly what steps to take. The Gitflow diagram shows 'hotfix' branches being opened against |
Since we have not heard back in 24 hours, I propose we merge this PR into |
@brylie Can you test it local? |
I just re-read the instructions you mentioned. We can merge this PR and then I will run the following commands: Next, include the bugfix in develop, too:
$ git checkout develop
Switched to branch 'develop'
$ git merge --no-ff hotfix-1.2.1
Merge made by recursive.
(Summary of changes)
|
@brylie ok, let's try |
Closes #2528
Note, we will need to make a new patch-level release for this hotfix.