Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update openstack terraform provider configuration #220

Closed
kayrus opened this issue Feb 1, 2021 · 3 comments
Closed

Update openstack terraform provider configuration #220

kayrus opened this issue Feb 1, 2021 · 3 comments
Assignees
Labels
area/usability Usability related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/openstack OpenStack platform/infrastructure priority/3 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)

Comments

@kayrus
Copy link
Contributor

kayrus commented Feb 1, 2021

How to categorize this issue?

/area usability
/kind enhancement
/priority normal
/platform openstack

What would you like to be added:

Current provider configuration should be adjusted:

provider "openstack" {
auth_url = "{{ required "openstack.authURL is required" .Values.openstack.authURL }}"
domain_name = "{{ required "openstack.domainName is required" .Values.openstack.domainName }}"
tenant_name = "{{ required "openstack.tenantName is required" .Values.openstack.tenantName }}"
region = "{{ required "openstack.region is required" .Values.openstack.region }}"
user_name = var.USER_NAME
password = var.PASSWORD
insecure = true
}

Insecure flag must be removed:

insecure    = true

And a max_retries should be set in order support the 429 response code with a Retry-After header.

Why is this needed:

  • Production environment must not contain the insecure=true parameter.
  • max_retries starting from Terrafrom OpenStack provider v1.36 will support the 429 response code and sleep accordingly. This is needed in order to decrease high amount of API calls, when a technical user password was changed and a user gets blocked by identity.
@kayrus kayrus added the kind/enhancement Enhancement, improvement, extension label Feb 1, 2021
@gardener-robot gardener-robot added area/usability Usability related platform/openstack OpenStack platform/infrastructure priority/normal labels Feb 1, 2021
@dkistner
Copy link
Member

dkistner commented Feb 2, 2021

/assign

We wait until openstack terraform provider which incorporate terraform-provider-openstack/terraform-provider-openstack#1159 is released and Terraformer will adopt this new release.

@dkistner
Copy link
Member

dkistner commented Feb 3, 2021

Status

@gardener-robot gardener-robot added priority/3 Priority (lower number equals higher priority) and removed priority/normal labels Mar 8, 2021
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 22, 2021
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Mar 24, 2022
@kayrus
Copy link
Contributor Author

kayrus commented Mar 7, 2023

it looks like the corresponding changes are already implemented:

max_retries = "{{ .openstack.maxApiCallRetries }}"
{{ if .openstack.insecure }}
insecure = true
{{ end }}

@kayrus kayrus closed this as completed Mar 7, 2023
@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/usability Usability related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/openstack OpenStack platform/infrastructure priority/3 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

No branches or pull requests

3 participants