-
Notifications
You must be signed in to change notification settings - Fork 871
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
Fix bug in cache when POSTing url with same key #13
Comments
lindydonna
added
area/examples
kind/bug
Some behavior is incorrect or out of spec
labels
Feb 8, 2018
@lukehoban Should I push this out until we've settled on our pulumi/cloud "refactor"? I imagine this sample might change quite a bit. |
lukehoban
added a commit
that referenced
this issue
Apr 23, 2018
Use latest @pulumi/cloud API, including not using `getEndpoint` in deployment code. Use 302 instead of 301 for redirects, since we allow changes to the indirection. Use config without `:config` part to avoid deprecation warning. Update the cache as well as the table in POST handler. Fixes #13.
lukehoban
added a commit
that referenced
this issue
Apr 23, 2018
Use latest @pulumi/cloud API, including not using `getEndpoint` in deployment code. Use 302 instead of 301 for redirects, since we allow changes to the indirection. Update the cache as well as the table in POST handler. Fixes #13.
lukehoban
added a commit
that referenced
this issue
Apr 23, 2018
Use latest @pulumi/cloud API, including not using `getEndpoint` in deployment code. Use 302 instead of 301 for redirects, since we allow changes to the indirection. Update the cache as well as the table in POST handler. Fixes #13.
ramene
pushed a commit
to ramene/pulumi-kubeflow-ml
that referenced
this issue
Sep 7, 2019
Use latest @pulumi/cloud API, including not using `getEndpoint` in deployment code. Use 302 instead of 301 for redirects, since we allow changes to the indirection. Update the cache as well as the table in POST handler. Fixes pulumi#13.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the UI allows a POST with a duplicate key which results in the Table being updated, the redis cache key also needs to be deleted.
The text was updated successfully, but these errors were encountered: