Skip to content
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

No warnings when attempting to overwrite immutable SWF activity registration parameters (e.g. defaultTaskList) #103

Closed
neil-rubens opened this issue Aug 2, 2013 · 3 comments
Assignees

Comments

@neil-rubens
Copy link

No warnings when attempting to overwrite immutable SWF activity registration parameters (e.g. defaultTaskList)

An example of problem that this may cause is as following. If taskList configurations are changed in code, but the version is not changed; the code will deploy just fine; yet the changes to the settings will not be propagated, and no warnings will be given. This is a frequently occurring case; and is quite difficult to discover/debug.

This issue is briefly discussed in this AWS Developer forum post.

@fulghum fulghum added the SWF label Aug 13, 2014
@breedloj breedloj self-assigned this Apr 21, 2016
@breedloj
Copy link
Contributor

Hey Neil,

I noticed that this issue has been open for nearly 3 years and I apologize for the lack of response. Is this still an issue for you?

@neil-rubens
Copy link
Author

Thanks for the reply. Currently I am not using SWF so am not sure if it is
still an issue.

On Fri, Apr 22, 2016, 02:19 Jonathan Breedlove notifications@github.com
wrote:

Hey Neil,

I noticed that this issue has been open for nearly 3 years and I apologize
for the lack of response. Is this still an issue for you?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#103 (comment)

@breedloj
Copy link
Contributor

Gotcha. SWF has seen a lot of changes over the past couple of years so I am going to close this for now. Feel free to re-open or open a new issue if you start using SWF again and run into issues. Thanks, and sorry again for the super delayed response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants