You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/03/06 13:46:19 UTC

[GitHub] [incubator-openwhisk] falkzoll commented on issue #4226: change the default action context to omit api key

falkzoll commented on issue #4226: change the default action context to omit api key
URL: https://github.com/apache/incubator-openwhisk/issues/4226#issuecomment-470112596
 
 
   Forwarding the API key only when it is really needed, means more security 👍 .
   
   One additional thought:
   From maintenance point of view, it would be comfortable to have the activation of backward compatibility breaking changes configurable :).
   
   This would allow the devops teams to deploy the actual code to their infrastructure and to communicate and activate the feature according to their individual schedules.
   The configurable activation would also make it easier to develop and test migration procedures (e.g. database updates) for an improved user experience when making the backward compatibility breaking change active.
   
   And in the worst case, it would allow a more easy roll back when something happens after it was activated, that was not foreseen. Changing the configuration and maybe a restart is simpler and faster than jumping back to a previous version which may need to be redeployed, first.
   
   I know the related PR is almost complete. But maybe this is something to be considered for future changes that also break backward compatibility :). What do you think?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services