-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Allow datastore key to be populated from a variable. #280
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - just a minor comment on the wording in the documentation.
b72aaee
to
850e7ba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great - thanks
become: yes | ||
copy: | ||
content: "{{ st2_datastore_key }}" | ||
dest: "{{ st2_datastore_key_file }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the content of the file changes we'll need to notify st2 to restart the services.
According to code below it's st2api
, but I guess that's incomplete as more StackStorm services might be using the crypto key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@armab added a restart to all of the st2 services
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Restarting all the st2 services is impractical here. We need only specific services that are using st2 datastore key.
Can you please figure out which may use it?
Previously, if installing StackStorm in a multi-node environment, it would generate a new datastore key on every node.
This change allows the datastore key to be specified as a variable
st2_datastore_key
then propagated to each host.By default, this variable is
null
and will result in a random key being generated (retaining same behavior).