到2018年3月1日将App Engine Python ssl升级到2.7.11 [英] Upgrade App Engine Python ssl to 2.7.11 by Mar 1, 2018

问题描述

我已收到来自GAE团队的电子邮件通知，需要升级到SSL 2.7.11。这是因为我的项目仍然使用2.7

但是在我的yaml文件中，ssl被设置为 latest

   - 名称：ssl 
版本：latest 
  

我的问题是

<1>我是否需要明确将版本更改为'2.7.11'？如果我继续使用 latest ，库会自动转到2.7.11

2）是否有可能在云端控制台中确认以检查ssl版本？我想确认yaml文件更新后发生的版本变化。

<3>是否有一组最小的测试来验证没有破坏的功能？

解决方案

对于＃1，恕我直言，最好使用明确的版本，而不是依靠默认值，如果可能的 - 它提供了一种控制迁移的机会：可以执行测试来发现问题，修复可以在没有压力的情况下发展，比在达到最后期限后发生火灾（或者由于任何原因更改默认值）更好。也实际上消除了＃2：）

对于＃2 - 我不知道在开发者控制台中有一席之地，但你可以暂时（只是为了得到答案） ：

• 在相关部分添加应用程序日志消息显示 sys.path 的应用程序代码。输出通常包括您的应用程序中使用的每个运行时提供的库的路径，其中大多数（如果不是全部的话）包含片段中的版本号，如 third_party / ssl-2.7 。例如，请参阅谷歌应用程序引擎yaml-3.10错误。


• 在 ssl 库中强制崩溃（例如通过传递一些无效参数） - 堆栈跟踪还包括上述＃b
  

对于＃3我不知道一些官方或推荐的测试，我只能建议测试您的应用程序是否继续工作如预期的那样。

I have received an notification in email from GAE team about the need to upgrade to SSL 2.7.11. It is because my projects are still using 2.7

However in my yaml file, the ssl is set to latest

 - name: ssl
  version: latest

My questions are

1) Do I need to change the version explicitly to '2.7.11'? If I stay with latest will the library be automatically rolled over to 2.7.11

2) Is it possible to identify in cloud console to check the ssl version? I want to confirm the change of version has taken place after the yaml file is updated

3) Is there a minimum set of tests that should be performed to verify there is no breakage in term of functionality?

解决方案

For #1, IMHO it's preferable to use an explicit version rather than relying on defaults, if possible - it offers a chance to somehow control the migration: tests can be executed to catch problems and fixes can be developed without pressure, better than putting out fires after the deadline is reached (or when defaults are changed, for whatever reason). Also practically eliminates #2 :)

For #2 - I don't know of a place in the developer console, but you could temporarily (just to get the answer) either:

• add an app log message displaying sys.path in a related portion of your app code. The output typically includes paths to each of the runtime-provided libraries used in your app, most (if not all) of which include the version number in snippets like third_party/ssl-2.7. See, for example, google app engine yaml-3.10 error.
• force a crash in the ssl library (by passing some invalid arguments, for example) - the stack trace also includes the above-mentioned snippets.

For #3 I don't know of some official or recommended tests, I can only suggest testing that your app keeps working as expected.

这篇关于到2018年3月1日将App Engine Python ssl升级到2.7.11的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！