Error: Cannot determine region: set in this resource, or set provider-level 'region' or 'zone'.

I was under the impression that the region and the zones etc are set in the terraform commands automatically but when I run terraform plan -out plan.out it returns the error that is in the title of this issue: Error: Cannot determine region: set in this resource, or set provider-level 'region' or 'zone'.
What am I doing wrong?

Yes, that's also what I thought. Perhaps a very recent version has changed that.
Could you paste more logs? Or is it the first error line after running terraform cmd?

Yes, that's also what I thought. Perhaps a very recent version has changed that.
Could you paste more logs? Or is it the first error line after running terraform cmd?

It happens when I type this command terraform plan -out plan.out

It happens when I type this command terraform plan -out plan.out

perhaps there is a way that I could help you trouble shoot it?

perhaps there is a way that I could help you trouble shoot it?

please print the full log of the command output or provide a screenshot
On Tue, Jan 12, 2021 at 1:41 AM Johannes Castner<EMAIL_ADDRESS>wrote:

perhaps there is a way that I could help you trouble shoot it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-758534327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC5ENS6XUHA3QYY2D4TSZQKNFANCNFSM4V2N2TFQ
.

please print the full log of the command output or provide a screenshot
On Tue, Jan 12, 2021 at 1:41 AM Johannes Castner<EMAIL_ADDRESS>wrote:

perhaps there is a way that I could help you trouble shoot it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-758534327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC5ENS6XUHA3QYY2D4TSZQKNFANCNFSM4V2N2TFQ
.

I hope that this is more insightful to you than it is to me?  This is all I get:
$ terraform plan -out plan.out
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
module.terraform-gke-blockchain.data.google_project.blockchain_cluster: Refreshing state...
data.google_client_config.current: Refreshing state...
module.terraform-gke-blockchain.data.google_compute_network.default-network: Refreshing state...
module.terraform-gke-blockchain.data.google_compute_subnetwork.default-subnetwork: Refreshing state...
Error: Cannot determine region: set in this resource, or set provider-level 'region' or 'zone'.
jw@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$`

I hope that this is more insightful to you than it is to me?  This is all I get:
$ terraform plan -out plan.out
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
module.terraform-gke-blockchain.data.google_project.blockchain_cluster: Refreshing state...
data.google_client_config.current: Refreshing state...
module.terraform-gke-blockchain.data.google_compute_network.default-network: Refreshing state...
module.terraform-gke-blockchain.data.google_compute_subnetwork.default-subnetwork: Refreshing state...
Error: Cannot determine region: set in this resource, or set provider-level 'region' or 'zone'.
jw@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$`

When I change my terraform.tfvars file to look like this:
organization_id=******** billing_account="********"<EMAIL_ADDRESS>polkadot_validator_name="MyName" polkadot_version="v0.8.26" chain="polkadot" polkadot_telemetry_url="wss://telemetry-backend.w3f.community/submit"
Then I get the following error:
$ terraform plan -out plan.out Refreshing Terraform state in-memory prior to plan... The refreshed state will be used to calculate this plan, but will not be persisted to local or remote state storage. data.google_client_config.current: Refreshing state... Warning: Value for undeclared variable The root module does not declare a variable named "organization_id" but a value was found in file "terraform.tfvars". To use this value, add a "variable" block to the configuration. Using a variables file to set an undeclared variable is deprecated and will become an error in a future release. If you wish to provide certain "global" settings to all configurations in your organization, use TF_VAR_... environment variables to set these instead. Error: Error in function call   on .terraform/modules/terraform-gke-blockchain/gcp.tf line 5, in provider "google":    5:   credentials = file(var.terraform_service_account_credentials)     |----------------     | var.terraform_service_account_credentials is<EMAIL_ADDRESS>Call to function "file" failed: no file exists at<EMAIL_ADDRESS>
I obviously misunderstand some of the instructions in the Hardening section.

When I change my terraform.tfvars file to look like this:
organization_id=******** billing_account="********"<EMAIL_ADDRESS>polkadot_validator_name="MyName" polkadot_version="v0.8.26" chain="polkadot" polkadot_telemetry_url="wss://telemetry-backend.w3f.community/submit"
Then I get the following error:
$ terraform plan -out plan.out Refreshing Terraform state in-memory prior to plan... The refreshed state will be used to calculate this plan, but will not be persisted to local or remote state storage. data.google_client_config.current: Refreshing state... Warning: Value for undeclared variable The root module does not declare a variable named "organization_id" but a value was found in file "terraform.tfvars". To use this value, add a "variable" block to the configuration. Using a variables file to set an undeclared variable is deprecated and will become an error in a future release. If you wish to provide certain "global" settings to all configurations in your organization, use TF_VAR_... environment variables to set these instead. Error: Error in function call   on .terraform/modules/terraform-gke-blockchain/gcp.tf line 5, in provider "google":    5:   credentials = file(var.terraform_service_account_credentials)     |----------------     | var.terraform_service_account_credentials is<EMAIL_ADDRESS>Call to function "file" failed: no file exists at<EMAIL_ADDRESS>
I obviously misunderstand some of the instructions in the Hardening section.

This is indeed not very clear, the parameter should be set to the path to the json key file for the service account, not the service account name.
See instructions on how to download this file:
https://cloud.google.com/iam/docs/creating-managing-service-account-keys
Once you do this, it may work better. If you still have trouble with region, you can also add this line to your terraform.tfvars:
region="us-west1"

This is indeed not very clear, the parameter should be set to the path to the json key file for the service account, not the service account name.
See instructions on how to download this file:
https://cloud.google.com/iam/docs/creating-managing-service-account-keys
Once you do this, it may work better. If you still have trouble with region, you can also add this line to your terraform.tfvars:
region="us-west1"

Also, I just realized the default region string was empty in variables.tf. I am fixing it so both methods should work if you pull the latest code.

Also, I just realized the default region string was empty in variables.tf. I am fixing it so both methods should work if you pull the latest code.

Hello,
So now my terraform.tfvars file looks like this:
terraform_service_account_credentials="gs://MY_BUCKET/my-validator.json"
organization_id=***billing_account=""polkadot_validator_name="BudFox
testValidator"polkadot_version="v0.8.0"chain="polkadot"
polkadot_telemetry_url="wss://telemetry-backend.w3f.community/submit"
The "MY_BUCKET" variable is a valid bucket with a valid key json file.
The error that I'm getting now is as follows:
my-user-id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.outRefreshing Terraform state in-memory prior to
plan...The refreshed state will be used to calculate this plan, but will
not bepersisted to local or remote state
storage.data.google_client_config.current:
Refreshing state...Warning: Value for undeclared variableThe root module
does not declare a variable named "organization_id" but avalue was found in
file "terraform.tfvars". To use this value, add a"variable" block to the
configuration.Using a variables file to set an undeclared variable is
deprecated and willbecome an error in a future release. If you wish to
provide certain "global"settings to all configurations in your
organization, use TF_VAR_...environment variables to set these instead.Error:
Error in function call on .terraform/modules/terraform-gke-blockchain/gcp.tf
line 5, in provider "google": 5: credentials = file(
var.terraform_service_account_credentials) |---------------- |
var.terraform_service_account_credentials is
"gs://MY_BUCKET/my-validator.json"Call to function "file" failed: no file
exists atgs:/MY_BUCKET/my-validator.json.
It appears as though it can't find the file?
Please let me know what I'm doing wrong!
Johannes
On Thu, Jan 14, 2021 at 6:25 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

This is indeed not very clear, the parameter should be set to the path to
the json key file for the service account, not the service account name.
See instructions on how to download this file:
https://cloud.google.com/iam/docs/creating-managing-service-account-keys
Once you do this, it may work better. If you still have trouble with
region, you can also add this line to your terraform.tfvars:
region="us-west1"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-759955952,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEID447MEZ3BCNZFV2BCDSZ2E7JANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

Hello,
So now my terraform.tfvars file looks like this:
terraform_service_account_credentials="gs://MY_BUCKET/my-validator.json"
organization_id=***billing_account=""polkadot_validator_name="BudFox
testValidator"polkadot_version="v0.8.0"chain="polkadot"
polkadot_telemetry_url="wss://telemetry-backend.w3f.community/submit"
The "MY_BUCKET" variable is a valid bucket with a valid key json file.
The error that I'm getting now is as follows:
my-user-id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.outRefreshing Terraform state in-memory prior to
plan...The refreshed state will be used to calculate this plan, but will
not bepersisted to local or remote state
storage.data.google_client_config.current:
Refreshing state...Warning: Value for undeclared variableThe root module
does not declare a variable named "organization_id" but avalue was found in
file "terraform.tfvars". To use this value, add a"variable" block to the
configuration.Using a variables file to set an undeclared variable is
deprecated and willbecome an error in a future release. If you wish to
provide certain "global"settings to all configurations in your
organization, use TF_VAR_...environment variables to set these instead.Error:
Error in function call on .terraform/modules/terraform-gke-blockchain/gcp.tf
line 5, in provider "google": 5: credentials = file(
var.terraform_service_account_credentials) |---------------- |
var.terraform_service_account_credentials is
"gs://MY_BUCKET/my-validator.json"Call to function "file" failed: no file
exists atgs:/MY_BUCKET/my-validator.json.
It appears as though it can't find the file?
Please let me know what I'm doing wrong!
Johannes
On Thu, Jan 14, 2021 at 6:25 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

This is indeed not very clear, the parameter should be set to the path to
the json key file for the service account, not the service account name.
See instructions on how to download this file:
https://cloud.google.com/iam/docs/creating-managing-service-account-keys
Once you do this, it may work better. If you still have trouble with
region, you can also add this line to your terraform.tfvars:
region="us-west1"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-759955952,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEID447MEZ3BCNZFV2BCDSZ2E7JANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and default values.
As for the terraform_service_account_credentials, it should not be in a bucket. It should literally be in your filesystem. You can put it in the folder where you run the command, as my-validator.json then put the following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"

then it will work.

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and default values.
As for the terraform_service_account_credentials, it should not be in a bucket. It should literally be in your filesystem. You can put it in the folder where you run the command, as my-validator.json then put the following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"

then it will work.

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out
module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [10s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [20s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine API
has not been used in project 2*******4 before or it is disabled. Enable it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've never
seen before ...I don't understand how to handle this?  I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and
default values.
As for the terraform_service_account_credentials, it should not be in a
bucket. It should literally be in your filesystem. You can put it in the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out
module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [10s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [20s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine API
has not been used in project 2*******4 before or it is disabled. Enable it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've never
seen before ...I don't understand how to handle this?  I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and
default values.
As for the terraform_service_account_credentials, it should not be in a
bucket. It should literally be in your filesystem. You can put it in the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

Yes, in that mode, terraform creates a new project for you and enables the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner<EMAIL_ADDRESS>wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out
module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [10s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [20s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine API
has not been used in project 2*******4 before or it is disabled. Enable it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've never
seen before ...I don't understand how to handle this? I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and
default values.
As for the terraform_service_account_credentials, it should not be in a
bucket. It should literally be in your filesystem. You can put it in the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ
.

Yes, in that mode, terraform creates a new project for you and enables the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner<EMAIL_ADDRESS>wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out
module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [10s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Still creating... [20s
elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:
Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine API
has not been used in project 2*******4 before or it is disabled. Enable it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've never
seen before ...I don't understand how to handle this? I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and
default values.
As for the terraform_service_account_credentials, it should not be in a
bucket. It should literally be in your filesystem. You can put it in the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ
.

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply
"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:
Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 95 before or it is disabled. Enable it by
visiting https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=95
then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and enables the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error
when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine API
has not been used in project 2*******4 before or it is disabled. Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've
never
seen before ...I don't understand how to handle this? I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and
default values.
As for the terraform_service_account_credentials, it should not be in a
bucket. It should literally be in your filesystem. You can put it in
the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply
"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:
Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 95 before or it is disabled. Enable it by
visiting https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=95
then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and enables the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error
when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine API
has not been used in project 2*******4 before or it is disabled. Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've
never
seen before ...I don't understand how to handle this? I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables and
default values.
As for the terraform_service_account_credentials, it should not be in a
bucket. It should literally be in your filesystem. You can put it in
the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

It may be an issue with billing. Maybe try enabling the kubernetes api with
the console, see if you get an error.
Another thing you could try is to pass a project that already exists as a
parameter in terraform.tfvars
The module tries to create a project when it does not exist, but if you
pass one, it will just create the cluster in the pre-existing project.
On Tue, Jan 19, 2021 at 10:20 AM Johannes Castner<EMAIL_ADDRESS>wrote:

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply
"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:
Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 9***5 before or it is disabled. Enable it by
visiting
https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=9***5
then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and enables
the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner <
<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error
when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or
it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine
API
has not been used in project 2*******4 before or it is disabled. Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've
never
seen before ...I don't understand how to handle this? I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables
and
default values.
As for the terraform_service_account_credentials, it should not be
in a
bucket. It should literally be in your filesystem. You can put it in
the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763030426,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC4KK4NRNI2IKDYLRFDS2XEOXANCNFSM4V2N2TFQ
.

It may be an issue with billing. Maybe try enabling the kubernetes api with
the console, see if you get an error.
Another thing you could try is to pass a project that already exists as a
parameter in terraform.tfvars
The module tries to create a project when it does not exist, but if you
pass one, it will just create the cluster in the pre-existing project.
On Tue, Jan 19, 2021 at 10:20 AM Johannes Castner<EMAIL_ADDRESS>wrote:

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply
"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:
Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 9***5 before or it is disabled. Enable it by
visiting
https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=9***5
then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and enables
the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner <
<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error
when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before or
it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine
API
has not been used in project 2*******4 before or it is disabled. Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've
never
seen before ...I don't understand how to handle this? I've enabled the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables
and
default values.
As for the terraform_service_account_credentials, it should not be
in a
bucket. It should literally be in your filesystem. You can put it in
the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763030426,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC4KK4NRNI2IKDYLRFDS2XEOXANCNFSM4V2N2TFQ
.

Hi Nicolas,
Thank you for helping me; unfortunately it's still not working after I did
add the project variable. Now I'm getting this error message:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply "plan.out"
module.terraform-gke-blockchain.google_service_account.blockchain-server:
Creating...Error: Error creating service account: googleapi: Error 403:
Permission iam.serviceAccounts.create is required to perform this operation
on project projects/924950478415.,
forbiddenmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
What's missing now?!
Johannes
On Tue, Jan 19, 2021 at 6:26 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

It may be an issue with billing. Maybe try enabling the kubernetes api with
the console, see if you get an error.
Another thing you could try is to pass a project that already exists as a
parameter in terraform.tfvars
The module tries to create a project when it does not exist, but if you
pass one, it will just create the cluster in the pre-existing project.
On Tue, Jan 19, 2021 at 10:20 AM Johannes Castner <
<EMAIL_ADDRESS>wrote:

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply

"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:

Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 9***5 before or it is disabled. Enable it by
visiting

https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=9***5

then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and enables
the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and
it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner <
<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error
when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before
or
it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine
API
has not been used in project 2*******4 before or it is disabled.
Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've
never
seen before ...I don't understand how to handle this? I've enabled
the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to
it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables
and
default values.
As for the terraform_service_account_credentials, it should not be
in a
bucket. It should literally be in your filesystem. You can put it
in
the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763030426>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAAWXC4KK4NRNI2IKDYLRFDS2XEOXANCNFSM4V2N2TFQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763034259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEID6JDSNXX6HU4JHVR2DS2XFFRANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

Hi Nicolas,
Thank you for helping me; unfortunately it's still not working after I did
add the project variable. Now I'm getting this error message:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply "plan.out"
module.terraform-gke-blockchain.google_service_account.blockchain-server:
Creating...Error: Error creating service account: googleapi: Error 403:
Permission iam.serviceAccounts.create is required to perform this operation
on project projects/924950478415.,
forbiddenmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
What's missing now?!
Johannes
On Tue, Jan 19, 2021 at 6:26 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

It may be an issue with billing. Maybe try enabling the kubernetes api with
the console, see if you get an error.
Another thing you could try is to pass a project that already exists as a
parameter in terraform.tfvars
The module tries to create a project when it does not exist, but if you
pass one, it will just create the cluster in the pre-existing project.
On Tue, Jan 19, 2021 at 10:20 AM Johannes Castner <
<EMAIL_ADDRESS>wrote:

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply

"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:

Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 9***5 before or it is disabled. Enable it by
visiting

https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=9***5

then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and enables
the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time and
it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner <
<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error: Error
when
reading or editing Network Not Found : default: googleapi: Error 403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before
or
it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute Engine
API
has not been used in project 2*******4 before or it is disabled.
Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate to
our
systems and retry., accessNotConfigured d retry., accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform (fox-polkadot-validator)$
Where the project=number is a completely new project number that I've
never
seen before ...I don't understand how to handle this? I've enabled
the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access to
it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide, the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of variables
and
default values.
As for the terraform_service_account_credentials, it should not be
in a
bucket. It should literally be in your filesystem. You can put it
in
the
folder where you run the command, as my-validator.json then put the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763030426>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAAWXC4KK4NRNI2IKDYLRFDS2XEOXANCNFSM4V2N2TFQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763034259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPEID6JDSNXX6HU4JHVR2DS2XFFRANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

There are two ways
either use the hardening method with the terraform service account, and the
project will be created with the service account (but that seems to be
failing for you)
or use a pre-existing project using your own account
To use your own account, you have to remove the parameter
terraform_service_account_credentials from terraform.tfvars
Then it will pick the default (
https://github.com/midl-dev/polkadot-k8s/blob/master/terraform/variables.tf#L107)
which should exist on your system.
You may also need to remove the org id and billing account.
On Tue, Jan 19, 2021 at 10:46 AM Johannes Castner<EMAIL_ADDRESS>wrote:

Hi Nicolas,
Thank you for helping me; unfortunately it's still not working after I did
add the project variable. Now I'm getting this error message:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply "plan.out"
module.terraform-gke-blockchain.google_service_account.blockchain-server:
Creating...Error: Error creating service account: googleapi: Error 403:
Permission iam.serviceAccounts.create is required to perform this operation
on project projects/924950478415.,
forbiddenmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
What's missing now?!
Johannes
On Tue, Jan 19, 2021 at 6:26 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

It may be an issue with billing. Maybe try enabling the kubernetes api
with
the console, see if you get an error.
Another thing you could try is to pass a project that already exists as a
parameter in terraform.tfvars
The module tries to create a project when it does not exist, but if you
pass one, it will just create the cluster in the pre-existing project.
On Tue, Jan 19, 2021 at 10:20 AM Johannes Castner <
<EMAIL_ADDRESS>wrote:

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply

"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:

Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 9***5 before or it is disabled. Enable it by
visiting

https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=9***5

then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and
enables
the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time
and
it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner <
<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error:
Error
when
reading or editing Network Not Found : default: googleapi: Error
403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before
or
it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If
you
enabled
this API recently, wait a few minutes for the action to propagate
to
our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute
Engine
API
has not been used in project 2*******4 before or it is disabled.
Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate
to
our
systems and retry., accessNotConfigured d retry.,
accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform
(fox-polkadot-validator)$
Where the project=number is a completely new project number that
I've
never
seen before ...I don't understand how to handle this? I've enabled
the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access
to
it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide,
the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of
variables
and
default values.
As for the terraform_service_account_credentials, it should not
be
in a
bucket. It should literally be in your filesystem. You can put it
in
the
folder where you run the command, as my-validator.json then put
the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763030426
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC4KK4NRNI2IKDYLRFDS2XEOXANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763034259>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAPEID6JDSNXX6HU4JHVR2DS2XFFRANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763046607,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC7HIGQDNYVITIZKPILS2XHRDANCNFSM4V2N2TFQ
.

There are two ways
either use the hardening method with the terraform service account, and the
project will be created with the service account (but that seems to be
failing for you)
or use a pre-existing project using your own account
To use your own account, you have to remove the parameter
terraform_service_account_credentials from terraform.tfvars
Then it will pick the default (
https://github.com/midl-dev/polkadot-k8s/blob/master/terraform/variables.tf#L107)
which should exist on your system.
You may also need to remove the org id and billing account.
On Tue, Jan 19, 2021 at 10:46 AM Johannes Castner<EMAIL_ADDRESS>wrote:

Hi Nicolas,
Thank you for helping me; unfortunately it's still not working after I did
add the project variable. Now I'm getting this error message:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply "plan.out"
module.terraform-gke-blockchain.google_service_account.blockchain-server:
Creating...Error: Error creating service account: googleapi: Error 403:
Permission iam.serviceAccounts.create is required to perform this operation
on project projects/924950478415.,
forbiddenmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
What's missing now?!
Johannes
On Tue, Jan 19, 2021 at 6:26 PM Nicolas Ochem<EMAIL_ADDRESS>wrote:

It may be an issue with billing. Maybe try enabling the kubernetes api
with
the console, see if you get an error.
Another thing you could try is to pass a project that already exists as a
parameter in terraform.tfvars
The module tries to create a project when it does not exist, but if you
pass one, it will just create the cluster in the pre-existing project.
On Tue, Jan 19, 2021 at 10:20 AM Johannes Castner <
<EMAIL_ADDRESS>wrote:

Hi Nicolas,
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply

"plan.out"module.terraform-gke-blockchain.google_container_cluster.blockchain_cluster:

Creating...Error: googleapi: Error 403: Kubernetes Engine API has not
been used in project 9***5 before or it is disabled. Enable it by
visiting

https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=9***5

then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.,
accessNotConfiguredmy_id@cloudshell:~/polkadot-k8s/terraform
(my-polkadot-validator)$
It's not looking like it is converging, unfortunately...
Johannes
On Tue, Jan 19, 2021 at 4:10 PM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Yes, in that mode, terraform creates a new project for you and
enables
the
required apis.
But it may take a few minutes for the api to be created. Just run
terraform plan -out plan.out and terraform apply one more time
and
it
will converge.
On Tue, Jan 19, 2021 at 7:24 AM Johannes Castner <
<EMAIL_ADDRESS>
wrote:

Hello again,
So now this works:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform plan -out plan.out
but now I'm getting a problem with the next command:
my_id@cloudshell:~/polkadot-k8s/terraform (my-polkadot-validator)$
terraform apply plan.out

module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [10s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Still creating... [20s

elapsed]module.terraform-gke-blockchain.google_compute_router_nat.blockchain-nat[0]:

Creation complete after 22s [id=polkadot7754a27
ce8298707/us-central1/blockchain-router/blockchain-nat-1]Error:
Error
when
reading or editing Network Not Found : default: googleapi: Error
403:
Compute Engine API has not been used in project<PHONE_NUMBER>44 before
or
it
is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/comp
ute.googleapis.com/overview?project=203115488444 then retry. If
you
enabled
this API recently, wait a few minutes for the action to propagate
to
our
systems and retry., accessNotConfigured Enable it by visiting
https://console.developers.google.com/Error: Error when reading or
editing
Subnetwork Not Found : default: googleapi: Error 403: Compute
Engine
API
has not been used in project 2*******4 before or it is disabled.
Enable
it
by visiting https://console.developers.google.com/apis/api/c
ompute.googleapis.com/overview?project=2*****4 then retry. If you
enabled
this API recently, wait a few minutes for the action to propagate
to
our
systems and retry., accessNotConfigured d retry.,
accessNotConfigured
my_id@cloudshell:~/polkadot-k8s/terraform
(fox-polkadot-validator)$
Where the project=number is a completely new project number that
I've
never
seen before ...I don't understand how to handle this? I've enabled
the
Compute Engine in the project that we already have by now ..but
apparently terraform creates a new project and then has no access
to
it
for
creating compute engine instances?
Johannes
On Tue, Jan 19, 2021 at 5:08 AM Nicolas Ochem <
<EMAIL_ADDRESS>wrote:

Hi Johannes,
There is one mistake which I just fixed in the hardening guide,
the
correct name of the variable is org_id, not organization_id.
You can check terraform/variables.tf file for a list of
variables
and
default values.
As for the terraform_service_account_credentials, it should not
be
in a
bucket. It should literally be in your filesystem. You can put it
in
the
folder where you run the command, as my-validator.json then put
the
following in terraform.tfvars
terraform_service_account_credentials="my-validator.json"
then it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762604561

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEID2O55NF5WRLSGP443TS2UHU3ANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762913741

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC3DE234WDAICFYYVCDS2WPZPANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-762946431

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPEIDYDTSPF5QXSKF5YAFTS2WVGVANCNFSM4V2N2TFQ

.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by
understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763030426
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAAWXC4KK4NRNI2IKDYLRFDS2XEOXANCNFSM4V2N2TFQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763034259>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAPEID6JDSNXX6HU4JHVR2DS2XFFRANCNFSM4V2N2TFQ
.

--
Johannes

"Peace cannot be kept by force; it can only be achieved by understanding."

Albert Einstein
ᐧ

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/midl-dev/polkadot-k8s/issues/4#issuecomment-763046607,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWXC7HIGQDNYVITIZKPILS2XHRDANCNFSM4V2N2TFQ
.


Review HTTPS at UZH

(nothing to do in the repository, this is just a reminder)

Here is the working configuration file, which I'll then include in the examples folder:
LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so

<VirtualHost *:443>
    ServerName https://DOMAIN

    SSLEngine on
    SSLProxyEngine on

    SSLCertificateFile /some/path/to/file1.pem
    SSLCertificateKeyFile /some/path/to/file2.pem
    SSLCertificateChainFile /some/path/to/file3.pem

    ProxyPass / http://<IP_ADDRESS>:PORT/
    ProxyPassReverse / http://<IP_ADDRESS>:PORT/

    # These RequestHeader are not needed. Perhaps this is due to the fact that we run the node server via
    # PROTOCOL_HEADER=x-forwarded-proto HOST_HEADER=x-forwarded-host ORIGIN=http://fractal.mls.uzh.ch PORT=5175 node build
    # RequestHeader set X-Forwarded-Proto "https"
    # RequestHeader set X-Forwarded-Port "443"
</VirtualHost>


HHH-16761 Throw an appropriate error when an entity defines more @Id fields than its @IdClass

https://hibernate.atlassian.net/browse/HHH-16761

Nice.


BERT for Patents yields 1024 element array, but embedding_v1 is 64 element

How should I generate an embedding equivalent to embedding_v1? BERT for Patents generates a 1024 element embedding, but the embedding_v1 is a 64 element embedding.

The model to generate embedding_v1 has not been released, and we also haven't released pre-embedded patents with the BERT model in BigQuery.
You could experiment with learning a mapping from BERT to embedding_v1 with a linear layer - they should match up well because they're both based on text. embedding_v1 is a set-of-words unigram model.

Can you give some insight into how you dealt with limited window size for BERT?
Eg did you choose between abstract/patent/etc; Pool things? Something else?

Hi Saurabh,
We limited the window to claim 1.
Scott

From: Saurabh Bhatnagar @.>
Sent: Thursday, December 2, 2021 1:43 PM
To: google/patents-public-data @.>
Cc: sthorpe11 @.>; Author @.>
Subject: Re: [google/patents-public-data] BERT for Patents yields 1024 element array, but embedding_v1 is 64 element (#49)
Can you give some insight into how you dealt with limited window size for BERT?
Eg did you choose between abstract/patent/etc; Pool things? Something else?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fpatents-public-data%2Fissues%2F49%23issuecomment-984986213&data=04|01||f1a7f1780d5b4165a2f008d9b5d46c2f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637740746225068084|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=%2FAgVn6tHvK3T6%2BrbI2mBb3riU85pZ1dlXbK2dzRDpIg%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGKNX4UQBHUJKWIQ25X6AV3UO7K7ZANCNFSM47STZ6JQ&data=04|01||f1a7f1780d5b4165a2f008d9b5d46c2f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637740746225078042|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=p8ICdI2HV4Yjx3vLe9NHwIYMvpz7xmO6VYcby0jbHjM%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||f1a7f1780d5b4165a2f008d9b5d46c2f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637740746225078042|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=AppXLzUaP0L2Q3kdkfI9Iy325o3quxrPDpTY3hNlS5E%3D&reserved=0 or Androidhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||f1a7f1780d5b4165a2f008d9b5d46c2f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637740746225078042|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=PnJPsbAEHEag5VJIDBMrg82aGdMVMLe%2FcCYnwD3kftE%3D&reserved=0.

Thanks for that quick response.
This repo is a great resource.

This repo is great. Thank you! Any plans to release the model that generated embedding_v1 or the BERT pre-embedded patents?


MM-17515 - Updating settings-min css

Summary
MM-17515 - Updating settings-min css
Ticket Link
https://mattermost.atlassian.net/browse/MM-17515

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3382.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Thanks @asaadmahmood
Tested and it looks good to me.
Just one small nit (not sure if you missed it in the ticket?) but there is a period after Click to upload an image. on Profile picture and none of the other options have periods afterwards.
Are you able to remove the period?

Otherwise looks good. Confirmed that unit tests are done too.
QA will re-review/test post merge.

Test server destroyed

Updated the translation.

@asaadmahmood I don't see the text change in the committed files. Is that in another PR?

Hmmm good point, not sure if I forgot to push.
I'll push it here: https://github.com/mattermost/mattermost-webapp/pull/3390
As it was not strictly related to this PR anyways.


fix(clerk-js): Always display Danger section in OrganizationSettings

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

This PR fixes the layout shift caused by "Danger" section in Organization Settings
Before
https://github.com/clerkinc/javascript/assets/19269911/5a1b3d11-2e26-4fc6-9535-7ccff3ccf3cc
After
https://github.com/clerkinc/javascript/assets/19269911/6c9b2a40-f6de-4117-a35c-7d77bac8de3e

How this is looking before vs after?

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


[Bug][Vue SFC Playground] Playground has a memory leak problem

Vue version
undefined
Link to minimal reproduction
no need
Steps to reproduce
When switching the on and off states of "SSR", such a page crash problem will occur if the number of switches is too many.
https://github.com/vuejs/core/assets/70258597/d483aec8-e246-44b7-aec2-392b0bc2cb62
What is expected?
Hope the page doesn’t crash
What is actually happening?
I think it's caused by memory leak
System Info
No response
Any additional comments?
No response

There's no memory leak after profiling memory snapshots with the SSR toggle. The crash is likely caused by something else - that said, the playground is meant for experiments, it's unrealistic to toggle so many times and you can always just refresh the page as the state is preserved in the URL.


The hidden auto-update setting doesn't seem to work

To Reproduce
Install sleek 1.1.6, add "autoUpdate":false to ~/.config/sleek/user-preferences.json. Sleek will download v1.1.7 then remove the 1.1.6 AppImage.
Expected behavior
Auto-update should be skipped (perhaps notify the user of new version, but not download or install it).
Desktop

OS: Debian 11.3
Version of sleek: sleek-1.1.6 and sleek-1.1.7
Source: Github, (AppImage)

Write now I'm working around this by setting the immutable attr to the AppImage file.

The autoUpdate option will be disabled per default in future releases. Instead AppImage and MacOS builds will have a dedicated options in settings. It's already included in https://github.com/ransome1/sleek/releases/tag/v1.1.8-rc.4 but cannot be tested yet, as pre-releases are excluded from the auto update function.

thanks for the info, I'll be happy to test the 1.1.8 release once it's available!

@ransome1 Seems to be working in latest releases, thank you!


Default install fails with failure to download Zookeeper 3.4.12

Zookeeper released 3.4.14 and the link for 3.4.12 is now gone. As such to converge successfully, one needs to override:

node['zookeeper']['version'] to be 3.4.14
node['zookeeper']['checksum'] to be b14f7a0fece8bd34c7fffa46039e563ac5367607c612517aa7bd37306afbd1cd

@cbaenziger thanks for the heads-up. I’m a bit time-constrained, and not using the cookbook regularly at the moment; would you be willing to write a PR that updates the default values in this cookbook?
Thanks to how Apache handles versions, and that restarting ZooKeeper can mean potential data loss, this will be a major version for this cookbook.

@cbaenziger I got some time, finally, and with @hrak’s help, this was closed in #219, and released as v12.0.0.


NameError from list comprehension that refers to another name in the class definition

If there is a way to provide a hint about class scope for the following example, I think it would be very helpful (judging from the popularity on StackOverflow):
$ python -m friendly_traceback

Friendly Console version 0.2.19. [Python version: 3.9.0]

>>> class Foo:
...     n = 5
...     x = [i+n for i in range(5)]
...

Traceback (most recent call last):
  File "<friendly-console:1>", line 1, in <module>
    class Foo:
  File "<friendly-console:1>", line 3, in Foo
    x = [i+n for i in range(5)]
  File "<friendly-console:1>", line 3, in <listcomp>
    x = [i+n for i in range(5)]
NameError: name 'n' is not defined

I will have to explore ... but I don't think it is possible, based on the answers given on StackOverflow.  Given the frame where the exception is raised, I look at the local, global and nonlocal scopes, listing variables encountered. Since I don't see n listed when looking at the full explanation, I have the sneaking suspicion that it is not possible to identify n.  I'll have to do a bit of digging - I'll leave this case undetermined for now.

I will have to explore ... but I don't think it is possible, based on the answers given on StackOverflow.  Given the frame where the exception is raised, I look at the local, global and nonlocal scopes, listing variables encountered. Since I don't see n listed when looking at the full explanation, I have the sneaking suspicion that it is not possible to identify n.  I'll have to do a bit of digging - I'll leave this case undetermined for now.

Closing: there is no possibility of getting information about class scope.


semantic versioning request

Hello. I've been using the go-swagger generator (https://github.com/go-swagger/go-swagger) and Glide for package management. Go-swagger depends on go-flags but needs a recent version, more recent than v1. Would it be possible to add some additional semantic version tags (vx.y.z) to your source tree so that we can use Glide's semantic version mechanism over the more recent functionality changes in go-flags.
Thank you.

Pushed version 1.1 arbitrarily.


Implement OpenID Dynamic Client Registration API

Add support for OpenID Dynamic Client Registration API.

This is also now RFC 7591.


timeOut objects not cleared when using trycatch > 1.5.11 / hookit > 0.1.1

Hello,
I am not sure if that issue should be submitted here, but as I have spent over a day trying to figure out what my bug was, I think it at least deserved to be documented. :)
So, I use follow 0.12.1 for tracking changes. I am also using trycatch, which depends on hookit. After I updated from trycatch 1.5.11 to 1.5.19, follow suddenly stopped working, always breaking with "Timeout confirming database".
I figured out that a timeOut object was never cleared, because the setTimeOut was returning undefined. Further analysis showed that trycatch recently upgraded the hookit version, which seems to break the setTimeOut function used in follow.
Downgrading to trycatch 1.5.11 and enforcing hookit to 0.1.1 seems to do the trick for now.

@mickaeltr this is probably due to the fact that hookit is causing side-effects because it is overrding global functionality and making certain assumptions about it. I would post an issue with the author of the library :).

It looks like it has been fixed already in hookit 1.1.2 (or 1.1.3).
Sorry for the disturbance.


Feat/jupiter plans

Issue
https://github.com/gravitee-io/issues/issues/7991

🚀 CI was able to deploy the build of this PR, so you can now try it directly here
Notes: The deployed app is linked to the management API of APIM master. (Same login and password as APIM master)

📚  View the storybook of this branch here

Replaced with https://github.com/gravitee-io/gravitee-api-management/pull/2284 to execute e2e tests


Change naming of text

Changed text values to be more consistent for tasks. Capitalisation especially.
Closes #87.

Thank you


Fix audio tracks not looping

This fixes songs not looping because they got cleaned up before they had a chance to start anew.
Solves https://github.com/ppy/osu/issues/1522

@peppy is this ok now?

Have not yet had a chance to review this. No need to highlight me; I (or someone else) will get to it as time allows


Add condor manager CNAME DNS record to build server

As per the discussion in this issue: https://github.com/usegalaxy-eu/issues/issues/604

This only creates a new CNAME record for the build server and removes the unused one for the sn06. All our hosts use build. galaxy project.eu as their CONDOR_HOST.


Remove extra slash in link

does it make any difference?

@avneesh0612 my suggestion is to close the unnecessary pull requests, they create a mess

hmm yeah

does it make any difference?

not really, but it's looks better/more professional in my opinion, and also coz it's like that for Kira's links, it's better if we keep the same format, if you get what I mean.

@avneesh0612 my suggestion is to close the unnecessary pull requests, they create a mess

True, sorry for the inconvenience, but just in my opinion it looks better.

Should I delete the branch or will yall consider merging this in?

Should I delete the branch or will yall consider merging this in?

You can delete the branch

Should I delete the branch or will yall consider merging this in?

You can delete the branch

ok


Autocompletion for Generic Mapped Types in Typescript (Conditional: Based on First Parameter ,Second Parameter should get Valid Suggestions)

From @sarathkrrish on March 24, 2018 13:21
 interface rc {}

interface rc {
  parent1: {
    children: {
      child1: {
        props: {
          child1prop1: any;
          child1prop2: any;
        };
      },
      child2:{
        props: {
          child2prop1: any
        }
      }
    };
  };
}

//@ts-ignore
type ChildProp<T,S> = keyof rc[T]["children"][S]['props'];

declare interface sample<T extends keyof rc> {
   //@ts-ignore
  check<S extends keyof rc[T]["children"],F extends ChildProp<T,S>>(childid:S,propid:F);
}

Above one is declarations I am having. I am not sure issue or it is the feature, based on the first parameter in check method, I need to get valid autocomplete suggestions for the second parameter.
// Here I will get only child1 props as suggestions but not child2 props .
   var sample = sample<'parent1'>
      sample.check('child1','child1prop1')

VSCode is able to validate the code of first and second parameters of the check method.But it is unable to give autocompletion for the second parameter. Is it possible to provide that?
Copied from original issue: Microsoft/vscode#46464

The first @ts-ignore is suppressing errors that likely explain why you don't get proper intellisense. TypeScript cannot infer the keys of props from the expression as written. Someone in the TS community may know the correct way to write this


[FX-2127] Make the display title of ArtistSeriesRail configurable

https://artsyproduct.atlassian.net/browse/FX-2127
Problem
The ArtistSeriesRail — which shows artist series associated with a given artist — currently always shows a title of "More series by this artist". But we want to be able to choose a different display title depending on the context.
Solution

Make the display title configurable with an optional title prop
Fall back to a reasonable default if title is not supplied.

It seemed natural to me for the vanilla phrase "Artist Series" (spec'd in this ticket) to be the default title, and for other instances to supply a more specific title depending on the use case, so that's how this PR looks.
Before

After

Other usages

On the Artist Series page, retains the old title:

On the Artwork page, retains the old title:

Makes sense, and I agree that 'Artist Series' feels like the better fallback/default, vs. what sounds like a slightly more specific contextual phrasing of 'More series by this artist'.


Color

@bhough this includes the changes we discussed in the previous PR and some refactoring
Regarding -1 for tint & shade I would suggest we allow it since it is valid to do that. What I think would be cool are warnings that only show up in dev mode and are removed if polished is minified. Basically the same what React does. Then we can make polished accept weird inputs e.g. alpha of 1.1, but warn in dev mode about it. What do you think?

@mxstbr @bhough I needed to ignore some Flowtype checking in toColorString. I'm confident that this works fine and is rather a flow issue. I probably try to get help from someone of the flow team next week and see if we can fix it.
Should not block a release …


cleanup: log the image name and pool name

instead of logging the volumeID and the pool name. log the poolname and image name for better debugging and also change case of error message as per standard
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

@mergifyio rebase

@mergifyio rebase

@mergifyio rebase

@Mergifyio rebase


[IMPROVEMENT] Google Smart Lock is too intrusive in 2.3.0

Description
Let's add a button to call Google Smart Lock instead of opening by itself.
Devices and Versions
Your Rocket.Chat.Android version: 2.3.0.
Steps to reproduce

Today, only opens the Authentication screen and Google Smart Lock will show;

Expected Results

Open the authentication screen;
See Google Smart Lock icon and press it to be prompted;

Closed by #1334


Improve error handling. Fix logout endpoint. Handle sign-in and MFA errors.

closes #349
Changes described in each commit message.
Easier to review ignoring whitespace, especially users.py https://github.com/open-contracting/credere-backend/pull/389/files?w=1
Re: 403 vs 404 for get_user() dependency viz user enumeration: It already discloses the users's non-existence in the detail message, so might as well use 404.
And with this, I end the saga that I started with – trying to better handle login errors!
If after deploy, we witness new errors in Sentry that shouldn't be there (I'm not expecting any), we can just add them to except clauses, or update the Sentry configuration in settings.py (e.g. to not report HTTP 400 errors – in case bots are sending bad requests to endpoints, for example).

Not sure why that test is failing

I'll see, and then merge. Could just be that I let too few seconds go by in the test fixtures. Works locally.


test: testing Linkage Checker with Gradle

Does it detect linkage errors in gax-grpc?
Testing Linkage Checker with Gradle. Document: https://github.com/GoogleCloudPlatform/cloud-opensource-java/wiki/Linkage-Checker-with-Gradle.

For "Kokoro - Test: Java 8", it ran LinkageCheckerMain successfully. So successful that it did not exit with non-zero status even though there are linkage errors.


RFE: please add TypeScript definitions

Other Cypress and esbuild plugins offer TS definitions, which are always helpful.

:) whoever needs TS definitions is welcome to open a PR to add them of course
Sent from my iPhone

On Nov 24, 2021, at 18:14, Kyle Getz @.***> wrote:

Other Cypress and esbuild plugins offer TS definitions, which are always helpful.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hey! I've opened a PR to address this, hope it helps :)

@JoaoTMDias Is this still being worked on? The PR looks like it's stalled.

Hey! I'm sorry I haven't been able to pay attention to this issue. I'll do the changes as soon as I can.

This can be closed, type definitions have been added


甚麼 should be converted to 什么, not 甚么

甚么 is listed in STPhrases.txt a few times, meaning that conversion from Trad -> Simp causes 甚麼 to become 甚么. (I'm not sure if this is intentional, though.)
干甚	幹甚
干甚么	幹甚麼
[...]
甚么	甚麼
甚么都干	甚麼都幹
[...]
葫芦里卖甚么药	葫蘆裏賣甚麼藥
葫芦里卖的甚么药	葫蘆裏賣的甚麼藥

Since 甚么 is very rare (and nonstandard) compared to 什么, it would make more sense to have the above cases of 甚 and 甚麼 correspond to 什 and 什么 instead.

I don't think it should. It's the author's choice to use a rare form of the word.
OpenCC should do nothing more than converting between the two standards: Simplified Chinese and Traditional Chinese. There's no mapping between 甚 and 什.
By the way, STPhrases.txt converts Simplified Chinese to Traditional, not the other way round.

Ah, I see. I was using the OpenCC site to convert from Traditional to Simplified, which returned 甚么 for 甚麼, and since STPhrases.txt was the only place where 甚麼 was listed, I assumed that was where the Traditional -> Simplified mappings were.
I think it's safe to say that 甚麼 is considered one of the two widely used Traditional Chinese forms of 什么, even if it's a common variant of 什麼 -  with this in mind, to have 甚麼 map to 什么 would better fit the aims of OpenCC (conversion between trad and simp) in my opinion.
My understanding is that a general mapping of 甚 <--> 什 (which would be wrong) wouldn't be necessary to map 甚麼 to 什么, but I'm open to corrections if that is not the case.