Giter Site home page Giter Site logo

Comments (4)

michaelbannister avatar michaelbannister commented on July 24, 2024 3

I've just hit upon this issue, but in the context of Google Cloud Functions, when it builds for Python 3.8, uses the compileall module which can't handle a modification time after 2147483647 (2038-01-19T03:14:07) – see https://bugs.python.org/issue34990

It would be helpful if the date chosen could be less far in the future!

Update (23 Aug 2020): Google has updated their buildpack for python38 to add the -f flag on execution of compileall so it ignores timestamps. The change isn't yet rolled out on Cloud Functions but should be soon, apparently.

from terraform-provider-archive.

rickiedu avatar rickiedu commented on July 24, 2024 2

Yes, an option to preserve modification times would be nice.

from terraform-provider-archive.

bboe avatar bboe commented on July 24, 2024

While I had no hand in the implementation for this feature, the reason for setting the modification time to something consistent is so that the resulting archive file is consistent across machines. Otherwise running terraform apply on two separate machines with identical content will result in needing to update the function despite nothing changing. To me that's desirable behavior. Furthermore, I'm about to start on a PR to make permissions consistent in the archive in order to resolve #34.

Perhaps you would like an option to preserve modification times. Maybe that would suffice for your needs?

from terraform-provider-archive.

WeatherGod avatar WeatherGod commented on July 24, 2024

I ran into this issue today. I have an AWS lambda method that is constructed from an archive_file. In the zip file, I have in addition to the source code a static data file. The code when run in lambda generates a zip archive containing, among other things, a copy of that static data file. The timestamp on the data file in the archive being set in the future would not be ideal for our customers.

It would be nice to 1) document this (I find the explanation quite reasonable). 2) perhaps provide an option to turn on mod time preservation? In the meantime, I should be able to force a particular timestamp programmatically.

from terraform-provider-archive.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.