有没有办法在不同的开发生命周期环境中使用SendGrid模板版本控制? [英] Is there a way to use SendGrid Template Versioning with different development life-cycle environments?

问题描述

SendGrid中的版本允许API客户端仅通过记录在此处，但是一次只能有一个版本的模板处于活动"状态.显然，用于生产应用程序的模板必须始终设置为活动状态，但是如何添加在即将发布的版本中使用的新模板版本呢?如何在我们的测试环境中利用模板版本来测试此非活动"版本? 在此处中讨论了该问题，但是当它关​​闭时，它似乎就被关闭并丢失了您开始关注链接.

Versioning in SendGrid allows API clients to make template requests only by template ID documented here, however, only one version of a template can be "Active" at a time. Obviously, the template used for our production applications needs to always be set to active, but what about adding a new template version we use in an upcoming release? How can I leverage template versions to test this "Inactive" version in our test environment? The issue was discussed here, but it seems to just be closed and lost when you start following the links.

如果无法指定版本控制，则只剩下几个选项，这些选项要求创建特定于环境的模板，并在发行完成后将其提升为生产特定的模板，或者为不同的SDLC环境创建单独的帐户，随着过程的进行迁移它们.

If there is no way to specify versioning, that only leaves a few options that require either creating environment specific templates and having them get promoted to the production specific template once a release is finished, or creating separate accounts for different SDLC environments and migrating them as the process moves forward.

这里也讨论了有关语言版本控制的问题，但这确实没有帮助我解决问题.

The issue was also discussed here in regards to language versioning, but it really doesn't help my problem.

鉴于SendGrid API提供的用于利用版本控制的工具，最佳实践是什么?使用不同的SDLC步骤命名模板似乎很难维护数百个模板(更不用说针对每个环境使用多个模板了).在过渡到生产时进行测试时，管理多个帐户似乎是一场噩梦.我只是在这里想念一些完全不明显的东西吗?

What is the best practice given the tools provided by SendGrid's API to leverage versioning? Having different SDLC step named template seems like a disaster to maintain with hundreds of templates(let alone multiple for each environment). Managing multiple accounts just seems like a nightmare when it comes to testing when moving to production. Am I just missing something completely obvious here?

推荐答案

我在SendGrid与技术代表进行了交谈，但他们的API或UI上没有此功能.一次只能激活"单个模板.您需要为每个环境使用单独的模板，或者需要从API使用者管理这些模板.如果有人读过此书，并对不同的解决方案有疑问，请随时发表，我将解释如何解决此问题以满足应用程序的需求.

I spoke with technical reps at SendGrid and this feature is not available from their API or UI. Only a single template can be "activated" at a time. You need a separate template for every environment, or the templates need to be managed from your API consumer. If anyone reads this and has questions about different solutions, feel free to post and I'll explain how I resolved this for my application`s needs.

这篇关于有没有办法在不同的开发生命周期环境中使用SendGrid模板版本控制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！