Unable to use mysql in the same plan which creates MySQL server
I want to create an AWS RDS instance and then want to manage db users with the terraform. So first, I have created a RDS instance and then initialised the mysql provider with the created RDS instance to use it further for user management. But mysql provider is taking default endpoint (127.0.0.1) to connect during planning phase. Following is my code
resource "aws_rds_cluster" "default" {
name = "${var.name}"
master_username = "${var.master_username}"
master_password = "${random_string.password.result}"
.
.
.
}
provider "mysql" {
endpoint = "${aws_rds_cluster.default.endpoint}"
username = "${aws_rds_cluster.default.master_username}"
password = "${random_string.password.result}"
}
mysql terraform terraform-provider-aws
asked Nov 21 at 6:24
rkghost
334
add a comment |
I want to create an AWS RDS instance and then want to manage db users with the terraform. So first, I have created a RDS instance and then initialised the mysql provider with the created RDS instance to use it further for user management. But mysql provider is taking default endpoint (127.0.0.1) to connect during planning phase. Following is my code
resource "aws_rds_cluster" "default" {
name = "${var.name}"
master_username = "${var.master_username}"
master_password = "${random_string.password.result}"
.
.
.
}
provider "mysql" {
endpoint = "${aws_rds_cluster.default.endpoint}"
username = "${aws_rds_cluster.default.master_username}"
password = "${random_string.password.result}"
}
mysql terraform terraform-provider-aws
asked Nov 21 at 6:24
rkghost
334
add a comment |
I want to create an AWS RDS instance and then want to manage db users with the terraform. So first, I have created a RDS instance and then initialised the mysql provider with the created RDS instance to use it further for user management. But mysql provider is taking default endpoint (127.0.0.1) to connect during planning phase. Following is my code
resource "aws_rds_cluster" "default" {
name = "${var.name}"
master_username = "${var.master_username}"
master_password = "${random_string.password.result}"
.
.
.
}
provider "mysql" {
endpoint = "${aws_rds_cluster.default.endpoint}"
username = "${aws_rds_cluster.default.master_username}"
password = "${random_string.password.result}"
}
mysql terraform terraform-provider-aws
asked Nov 21 at 6:24
rkghost
334
I want to create an AWS RDS instance and then want to manage db users with the terraform. So first, I have created a RDS instance and then initialised the mysql provider with the created RDS instance to use it further for user management. But mysql provider is taking default endpoint (127.0.0.1) to connect during planning phase. Following is my code
resource "aws_rds_cluster" "default" {
name = "${var.name}"
master_username = "${var.master_username}"
master_password = "${random_string.password.result}"
.
.
.
}
provider "mysql" {
endpoint = "${aws_rds_cluster.default.endpoint}"
username = "${aws_rds_cluster.default.master_username}"
password = "${random_string.password.result}"
}
mysql terraform terraform-provider-aws
mysql terraform terraform-provider-aws
asked Nov 21 at 6:24
rkghost
334
asked Nov 21 at 6:24
rkghost
334
asked Nov 21 at 6:24
rkghost
334
asked Nov 21 at 6:24
rkghost
334
asked Nov 21 at 6:24
rkghost
334
334
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
As per terraform's current implementation, To initialize MySQL provider, MySQL has to exist first. That's why it's failing because during plan phase your RDS instance doesn't exist. There is already an open issue (https://github.com/hashicorp/terraform/issues/18720) for this on terraform GitHub repo.
So to manage it, you have to first create RDS instance and then you can use the credentials of that to initialize the mysql provider
answered Nov 21 at 6:27
Ram
385112
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53406325%2funable-to-use-mysql-in-the-same-plan-which-creates-mysql-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As per terraform's current implementation, To initialize MySQL provider, MySQL has to exist first. That's why it's failing because during plan phase your RDS instance doesn't exist. There is already an open issue (https://github.com/hashicorp/terraform/issues/18720) for this on terraform GitHub repo.
So to manage it, you have to first create RDS instance and then you can use the credentials of that to initialize the mysql provider
answered Nov 21 at 6:27
Ram
385112
add a comment |
As per terraform's current implementation, To initialize MySQL provider, MySQL has to exist first. That's why it's failing because during plan phase your RDS instance doesn't exist. There is already an open issue (https://github.com/hashicorp/terraform/issues/18720) for this on terraform GitHub repo.
So to manage it, you have to first create RDS instance and then you can use the credentials of that to initialize the mysql provider
answered Nov 21 at 6:27
Ram
385112
add a comment |
As per terraform's current implementation, To initialize MySQL provider, MySQL has to exist first. That's why it's failing because during plan phase your RDS instance doesn't exist. There is already an open issue (https://github.com/hashicorp/terraform/issues/18720) for this on terraform GitHub repo.
So to manage it, you have to first create RDS instance and then you can use the credentials of that to initialize the mysql provider
answered Nov 21 at 6:27
Ram
385112
As per terraform's current implementation, To initialize MySQL provider, MySQL has to exist first. That's why it's failing because during plan phase your RDS instance doesn't exist. There is already an open issue (https://github.com/hashicorp/terraform/issues/18720) for this on terraform GitHub repo.
So to manage it, you have to first create RDS instance and then you can use the credentials of that to initialize the mysql provider
answered Nov 21 at 6:27
Ram
385112
answered Nov 21 at 6:27
Ram
385112
answered Nov 21 at 6:27
Ram
385112
answered Nov 21 at 6:27
Ram
385112
385112
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53406325%2funable-to-use-mysql-in-the-same-plan-which-creates-mysql-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
