Skip to content
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.

Fixes evaluation of the file suffix for functions with base64 content type #987

Merged
merged 2 commits into from
Jan 24, 2019

Conversation

me-viper
Copy link
Contributor

@me-viper me-viper commented Jan 24, 2019

Issue Ref: Fixes #986

Description:

Fixes getFileName function to infer file suffix for base64 encoded functions.

TODOs:

  • Ready to review
  • Automated Tests
    - [ ] Docs

Copy link
Contributor

@andresmgot andresmgot left a comment

Choose a reason for hiding this comment

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

Thanks for the patch @me-viper! I am curious, what's your use case for this? Why sending the content of the function as base64 if it's not a binary?

@me-viper
Copy link
Contributor Author

Nothing exciting really. We are extending our system to support kubeless. For historical reasons our implementation is passing functions around in base64 so it made sense to use out of box base64 support rather than do additional conversions.

@andresmgot
Copy link
Contributor

Understood. Let me merge this. Until the next release is available you can use the latest image tag for the function-controller if you want to use this. Thanks again for contributing!

@andresmgot andresmgot merged commit daf1814 into vmware-archive:master Jan 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

File suffix for functions with content type base64 is not set
2 participants