This repository has been archived by the owner on May 31, 2023. It is now read-only.
Add ability to generate API keys #49
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch adds the ability to generate API keys which can be used in automation later in the same playbook, or by entirely different playbooks. Given that the API keys are generated once-off and not retrievable after the fact, we store the keys on the deployment host to allow retrieval and re-use.
|
Wow! This is great! 👍 |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch adds the ability to generate API keys
which can be used in automation later in the
same playbook, or by entirely different playbooks.
Given that the API keys are generated once-off
and not retrievable after the fact, we store the
keys on the deployment host to allow retrieval
and re-use.