-
Notifications
You must be signed in to change notification settings - Fork 55
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
rfc: Terraform provider #2613
rfc: Terraform provider #2613
Conversation
✅ Deploy Preview for constellation-docs canceled.
|
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
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
c2ac55d
to
4045cc0
Compare
Signed-off-by: Moritz Sanft <[email protected]>
Co-authored-by: Adrian Stobbe <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
Co-authored-by: Adrian Stobbe <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
Signed-off-by: Moritz Sanft <[email protected]>
4045cc0
to
e80b8a5
Compare
master_secret = "foo" # updating this would force recreation of the cluster | ||
init_secret = "bar" # maybe derive from master_secret, updating this would force recreation of the cluster |
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.
Do I understand correctly that the user generates these secrets and pastes them into this TF config?
If so, is it common to have such secrets in a TF config? Or should they come from input variables, env variables, etc.?
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.
You could use the Terraform random
provider (what we currently do) to generate this, load them from your HashiCorp vault by using the corresponding provider, etc.
I don't think you would expose them in the configuration files usually, but only in the state, which can be stored remotely, etc. and only have a reference to it, e.g. by using the random
provider, in the configuration files - But the RFC should be agnostic of where the value comes from actually. When documenting our provider we could mention some recommendations of how secrets can be provisioned.
* rfc: Terraform provider Signed-off-by: Moritz Sanft <[email protected]> * fix typo Co-authored-by: Adrian Stobbe <[email protected]> * rfc: annotate fields that force recreation Signed-off-by: Moritz Sanft <[email protected]> * reword "cluster applying" Co-authored-by: Adrian Stobbe <[email protected]> * rfc: resembles -> declares Signed-off-by: Moritz Sanft <[email protected]> * rfc: connect dangling sentence Signed-off-by: Moritz Sanft <[email protected]> * rfc: indicate sensitive state Signed-off-by: Moritz Sanft <[email protected]> * rfc: warn about PVs on recreation Signed-off-by: Moritz Sanft <[email protected]> * rfc: idempotent -> nilpotent Signed-off-by: Moritz Sanft <[email protected]> * rfc: reword deletion Signed-off-by: Moritz Sanft <[email protected]> * rfc: mention resource outputs Signed-off-by: Moritz Sanft <[email protected]> --------- Signed-off-by: Moritz Sanft <[email protected]> Co-authored-by: Adrian Stobbe <[email protected]>
* rfc: Terraform provider Signed-off-by: Moritz Sanft <[email protected]> * fix typo Co-authored-by: Adrian Stobbe <[email protected]> * rfc: annotate fields that force recreation Signed-off-by: Moritz Sanft <[email protected]> * reword "cluster applying" Co-authored-by: Adrian Stobbe <[email protected]> * rfc: resembles -> declares Signed-off-by: Moritz Sanft <[email protected]> * rfc: connect dangling sentence Signed-off-by: Moritz Sanft <[email protected]> * rfc: indicate sensitive state Signed-off-by: Moritz Sanft <[email protected]> * rfc: warn about PVs on recreation Signed-off-by: Moritz Sanft <[email protected]> * rfc: idempotent -> nilpotent Signed-off-by: Moritz Sanft <[email protected]> * rfc: reword deletion Signed-off-by: Moritz Sanft <[email protected]> * rfc: mention resource outputs Signed-off-by: Moritz Sanft <[email protected]> --------- Signed-off-by: Moritz Sanft <[email protected]> Co-authored-by: Adrian Stobbe <[email protected]>
* rfc: Terraform provider Signed-off-by: Moritz Sanft <[email protected]> * fix typo Co-authored-by: Adrian Stobbe <[email protected]> * rfc: annotate fields that force recreation Signed-off-by: Moritz Sanft <[email protected]> * reword "cluster applying" Co-authored-by: Adrian Stobbe <[email protected]> * rfc: resembles -> declares Signed-off-by: Moritz Sanft <[email protected]> * rfc: connect dangling sentence Signed-off-by: Moritz Sanft <[email protected]> * rfc: indicate sensitive state Signed-off-by: Moritz Sanft <[email protected]> * rfc: warn about PVs on recreation Signed-off-by: Moritz Sanft <[email protected]> * rfc: idempotent -> nilpotent Signed-off-by: Moritz Sanft <[email protected]> * rfc: reword deletion Signed-off-by: Moritz Sanft <[email protected]> * rfc: mention resource outputs Signed-off-by: Moritz Sanft <[email protected]> --------- Signed-off-by: Moritz Sanft <[email protected]> Co-authored-by: Adrian Stobbe <[email protected]>
Context
We want to determine how the Terraform provider should look in practice. This should not yet discuss implementation details, but rather a high-level overview of what the outcome should be.
Proposed change(s)
Additional info
Checklist