[Authentication] Resolve namespace during secret update #9068
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
When storing auth secret (like during
import mlrun), if the secret exist and we have a new secret (same name) to store, we go to the flow of updating it instead of creating it.There is a bug during secret update where namespace=None because we miss the namespace resolvement like here feb28bd#diff-61dbf2e7115b2faa269a79d1939db5eeebbc97204540b745b15db12133c49261R736
🛠️ Changes Made
_update_secretto resolve namespace✅ Checklist
🧪 Testing
reproduced the bug, then patched the system and saw it resolved.
🔗 References
🚨 Breaking Changes?
🔍️ Additional Notes