-
Notifications
You must be signed in to change notification settings - Fork 670
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
[Housekeeping] Cleanup UrlBlob Usage #4632
Comments
Thank you for opening your first issue here! 🛠 |
🤖 Hi @pvditt! I'm Dosu, a friendly bot here to assist you while we're waiting for our human maintainers. I can help you troubleshoot issues, answer your questions, and guide you on your contributor journey. So, feel free to ask away! Based on the information provided, it seems feasible to remove the deprecated To remove it, you can delete the /*
* flyteidl/service/admin.proto
*
* No description provided (generated by Swagger Codegen https://github.com/swagger-api/swagger-codegen)
*
* API version: version not set
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
*/
package flyteadmin
// Represents a string url and associated metadata used throughout the platform.
// type AdminUrlBlob struct {
// // Actual url value.
// Url string `json:"url,omitempty"`
// // Represents the size of the file accessible at the above url.
// Bytes string `json:"bytes,omitempty"`
// } Then, remove all references to Please note that this change could potentially break your code if there are any hidden dependencies on Regarding the specific reason why the If you need further assistance or have more questions, feel free to ask. SourcesThis response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
Describe the issue
Remove usages of deprecated UrlBlob. UrlBlob is not utilized in propellor nor console but is returned in FlyteAdmin endpoints such as GetExecutionData.
What if we do not do this?
Just code cleanliness - potentially some confusion on how errors are getting bubbled up to clients.
Related component(s)
Flyteidl, Flyteconsole, Flytepropellor, Flyteadmin
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: